WACRM is a self-hostable CRM template for WhatsApp. In version 0.7.0 and earlier, the profiles_update row-level security policy in supabase/migrations/017_account_sharing.sql permits authenticated users to modify their own account_role and account_id, allowing a viewer to self-promote or move into another tenant and then access or modify tenant resources. Separately, match_ai_knowledge_fts and match_ai_knowledge_semantic in supabase/migrations/030_ai_knowledge.sql run as SECURITY DEFINER, accept a caller-controlled p_account_id, and omit an is_account_member check, allowing an authenticated non-member to read another tenant's knowledge-base chunks. This vulnerability is fixed with commit e01f7ed37184f972ace8fb2da5c3e37e56a6050f.
CVE-2026-77240
This critical-severity CVE scores 9.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 80% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.9
- EG Score
- 9.9(medium)
- EG Risk
- 49(Track)EG Risk 49/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity99% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 20%
- KEV
- Not listed
Published
September 18, 2026
Last Modified
September 18, 2026
Advisory Details (3)
Auto-updated Sep 18, 2026Database-layer authorization bypasses (C1 + H2) · Advisory · ArnasDon/wacrm · GitHub
https://github.com/ArnasDon/wacrm/security/advisories/GHSA-fg5p-2qc3-jmxrfix(security): patch DB-layer authz bypasses (GHSA-fg5p-2qc3-jmxr)
Fix merged in ArnasDon/wacrm PR #350 on 2026-07-08 — awaiting tagged release
https://github.com/ArnasDon/wacrm/pull/350commit e01f7ed37184 (ArnasDon/wacrm)
Fix landed in ArnasDon/wacrm commit e01f7ed37184 — awaiting tagged release
https://github.com/ArnasDon/wacrm/commit/e01f7ed37184f972ace8fb2da5c3e37e56a6050fWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 6× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-20 22:19 UTCEG score recompute
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-19 19:52 UTCEG score recompute
- 2026-09-18 17:26 UTCEG score recompute
- 2026-09-18 16:49 UTCEG score recompute
- 2026-09-18 16:49 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-639
Frequently asked(5)
What is CVE-2026-77240?
When was CVE-2026-77240 disclosed?
Is CVE-2026-77240 actively exploited?
What is the CVSS score of CVE-2026-77240?
How do I remediate CVE-2026-77240?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-77240
Is Your Infrastructure Affected by CVE-2026-77240?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.