/

CVE-2026-77239

Severity:

HIGH RISK

(8.1)

Improper Authorization (CWE-285) in WACRM CRM Flows

CVE-2026-77239

Awaiting Analysis

Vulnerability type

Category:

Improper Authorization

CWE:

CWE-285

Impact:

Unauthorized workflow modification and outbound messaging

Severity:

HIGH RISK

(8.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

WACRM contains improper authorization checks in flow and automation routes that verify account membership but do not require the agent role for privileged operations. A user with viewer-level access may create, modify, activate, or delete workflows and trigger outbound WhatsApp actions through service-role database operations.

Affected context

The vulnerability affects WACRM deployments using flow and automation API routes where viewer access is accepted before service-role database operations are performed. It becomes risky when a read-only account can reach these endpoints and the application does not independently enforce the role required for writes or outbound actions.

Exploit preconditions

  • Attack surface: Flow and automation API routes
  • Required access: An authenticated account with viewer-level membership access
  • Trigger point: Requests that create, edit, activate, delete, or execute flows and automations
  • Why exploitation is possible: Membership checks occur without a corresponding agent-role authorization check, while service-role database operations bypass row-level security policies

Why this happens

The underlying bug is a failure to enforce authorization at the operation boundary. The application treats membership authentication as sufficient for privileged changes, then uses a service-role database client that bypasses normal row-level security controls. This maps to CWE-285: Improper Authorization, because the system does not verify that the authenticated principal has the role required for the requested action.

Potential impact

  • A viewer may modify or activate workflows
  • A viewer could delete flows or cause destructive configuration changes
  • Unauthorized automations may send outbound WhatsApp messages
  • Business processes and customer communications may be disrupted
  • Attackers could abuse trusted service-role operations to bypass data access policies

General mitigation guidance

Mitigation generally focuses on enforcing authorization for every privileged operation, including operations performed through service-role clients.

Common defensive patterns include:

  • Apply explicit role and permission checks at each flow and automation write endpoint
  • Use deny-by-default authorization for activation, deletion, and outbound actions
  • Avoid treating membership authentication as permission to modify resources
  • Minimize service-role database usage and constrain it to narrowly scoped operations
  • Preserve row-level security and enforce equivalent application-layer checks when elevated clients are unavoidable
  • Separate read-only and mutation routes, with distinct policy requirements
  • Require audit logging and review for workflow activation and outbound messaging

How teams detect issues like this

Organizations can look for this class of issue through:

  • Static analysis and code review checks for service-role clients used after membership-only authorization
  • Route-level policy reviews comparing required roles with the sensitivity of each operation
  • Tests that attempt privileged flow and automation actions using viewer accounts
  • Runtime monitoring for unexpected workflow changes, deletions, activations, or outbound message triggers
  • Policy enforcement requiring explicit authorization middleware on mutation and action endpoints
  • Automated review tools that flag authorization checks missing from privileged API paths

Sources

SourceLink
github.comgithub.com/ArnasDon/wacrm/commit/03e851bea56dcf6bb21ff1b80ba531372bf3269f
github.comgithub.com/ArnasDon/wacrm/pull/351
github.comgithub.com/ArnasDon/wacrm/security/advisories/GHSA-34q7-fv77-625j

Frequently asked

questions

An authenticated user with viewer-level account access may be able to exploit it when the affected routes are exposed and role enforcement is absent.

No. The relevant condition is access as a viewer or other membership role that is accepted by the vulnerable endpoints.

Enforce the required role and operation-specific permissions before performing any database write or outbound action, including when a service-role client is used.

Use deny-by-default authorization, test every sensitive route with lower-privileged accounts, minimize elevated database clients, and monitor privileged workflow activity.

Find out what's already
exploitable in your codebase.