CVE-2026-77239: WACRM: Service-role routes missing a role check
WACRM is a self-hostable CRM template for WhatsApp. In version 0.7.0 and earlier, WACRM flow and automation write routes authenticate account viewers but do not enforce the agent role before using a service-role database client that bypasses row-level security. In src/app/api/flows/[id]/route.ts, src/app/api/flows/[id]/activate/route.ts, and src/app/api/flows/route.ts, a viewer can create, edit, activate, or delete flows because membership-only checks are followed by service-role writes. In src/app/api/automations/route.ts and src/app/api/automations/engine/route.ts, a viewer can create active automations and trigger outbound WhatsApp actions without the role required by the underlying write policies. This can permit unauthorized workflow changes, destructive flow deletion, and outbound actions from a role intended to be read-only. This vulnerability is fixed with commit 03e851bea56dcf6bb21ff1b80ba531372bf3269f.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
WACRM (self-hostable CRM template for WhatsApp)to a version that resolves this vulnerability.Fixed in 0.7.0Patch 03e851bea56dcf6bb21ff1b80ba531372bf3269f - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 0.7.0Patch 03e851bea56dcf6bb21ff1b80ba531372bf3269f
Event History
Frequently Asked Questions
Who can exploit the issue?
Any authenticated account viewer can exploit the affected flow and automation write routes. The attacker does not need the agent role that should be required for these actions.
What actions can an unauthorized viewer perform?
A viewer can create, edit, activate, or delete flows. They can also create active automations and trigger outbound WhatsApp actions, enabling unauthorized workflow changes, destructive deletions, and messages or other outbound actions.
Which deployments are affected?
WACRM version 0.7.0 and earlier is affected. The issue applies where viewers can access the affected API routes, because those routes use a service-role database client after only checking account membership.
How can I remediate the issue?
Apply the fix in commit 03e851bea56dcf6bb21ff1b80ba531372bf3269f. If patching is not immediately possible, restrict or remove viewer access for accounts that must not be able to modify flows or create automations.