CVE-2026-77239— WACRM: Service-role routes missing a role check
Quick assessment
Affected
ArnasDon wacrm
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.
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
Get alerts for future matching vulnerabilities
Log in to subscribe
I. Basic Information for CVE-2026-77239
Vulnerability Information
Shenlong is analyzing...
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗
Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
Vulnerability Title
WACRM: Service-role routes missing a role check
Source: CVE Program / CVE List V5
Vulnerability Description
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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
Source: CVE Program / CVE List V5
Vulnerability Type
授权机制不恰当
Source: CVE Program / CVE List V5
Affected Products
II. Public POCs for CVE-2026-77239
| # | POC Description | Source Link | Shenlong Link |
|---|
AI-Generated POC
Premium
No public POC found.
Login to generate AI POCIII. Intelligence Information for CVE-2026-77239
请登录查看更多情报信息。
Patches & Fixes for CVE-2026-77239 (2)
Other References for CVE-2026-77239 (1)
IV. Related Vulnerabilities
Same weakness: CWE-285
-
CVE-2026-84076
IBM Guardium Data Protection is affected by multiple vulnera -
CVE-2026-84036
IBM Guardium Data Protection is affected by multiple vulnera -
CVE-2026-61833
zot: Bearer authentication maps DELETE to push scope, allowi -
CVE-2026-10030
IBM MQ Console is vulnerable to privilege escalation -
CVE-2026-67102
HCL BigFix Service Management is affected by multiple securi
V. Comments for CVE-2026-77239
No comments yet