# CVE-2026-77240: WACRM database authorization bypass in profiles and AI knowledge

Source: https://junglewise.ai/threats/cve-2026-77240-wacrm-is-a-self-hostable-crm-template-for-whatsapp-in-version-0-7  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-18. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-77240 · Severity: critical · CVSS 9.9 · Published 2026-09-18

WACRM is a WhatsApp CRM template that allows businesses to manage customer relationships. The vulnerability allows authenticated users to escalate their privileges within accounts or move between tenants without authorization, and to read confidential knowledge-base content belonging to other organizations. An attacker could impersonate administrators, access or modify customer data across multiple accounts, and steal proprietary information.

Technologies: [ArnasDon WACRM](https://junglewise.ai/threats/technologies/wacrm). Vendors: [ArnasDon](https://junglewise.ai/threats/vendors/arnasdon).

## Quick answers

**Is CVE-2026-77240 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-77240 being exploited in the wild.

**How severe is CVE-2026-77240?** Critical severity, with a CVSS score of 9.9, published 18 September 2026.

**Which products and versions are affected?** ArnasDon WACRM 0.7.0 and earlier.

**Is there a fix for CVE-2026-77240?** A patch was published on 2026-07-08: Fixed by commit e01f7ed37184f972ace8fb2da5c3e37e56a6050f Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-77240 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-77240?** Check whether you run ArnasDon WACRM at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

Two database-layer authorization flaws exist in Supabase migrations: (1) the profiles_update RLS policy allows authenticated users to directly modify account_role and account_id columns, enabling privilege escalation and tenant-switching; (2) the match_ai_knowledge_fts and match_ai_knowledge_semantic functions run as SECURITY DEFINER with caller-controlled p_account_id but lack is_account_member checks, allowing non-members to read other tenants' knowledge chunks. Both require authentication but no tenant membership. Patches address this via RLS triggers and changing the functions to SECURITY INVOKER mode.

## Affected products

- ArnasDon WACRM 0.7.0 and earlier

## Timeline

- 2026-09-18: disclosed: Published on NVD
- 2026-07-08: patched: Fixed by commit e01f7ed37184f972ace8fb2da5c3e37e56a6050f

## References

- [https://github.com/ArnasDon/wacrm/commit/e01f7ed37184f972ace8fb2da5c3e37e56a6050f](https://github.com/ArnasDon/wacrm/commit/e01f7ed37184f972ace8fb2da5c3e37e56a6050f)
- [https://github.com/ArnasDon/wacrm/pull/350](https://github.com/ArnasDon/wacrm/pull/350)

## Related threats

- [ArnasDon WACRM SSRF in automation send_webhook action](https://junglewise.ai/threats/cve-2026-67530-arnasdon-wacrm-ssrf-in-automation-send-webhook-action)
- [WACRM authorization bypass in automation engine](https://junglewise.ai/threats/cve-2026-49141-wacrm-authorization-bypass-in-automation-engine)