CVE-2026-77239

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 79% 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
37(Track)
EG Risk 37/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 computed
Severity81% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
21%
KEV
Not listed

Published

September 18, 2026

Last Modified

September 18, 2026

Advisory Details (3)

Auto-updated Sep 18, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit.
github_commit

commit 03e851bea56d (ArnasDon/wacrm)

Fix landed in ArnasDon/wacrm commit 03e851bea56d — awaiting tagged release

https://github.com/ArnasDon/wacrm/commit/03e851bea56dcf6bb21ff1b80ba531372bf3269f
github_pr

fix(security): enforce agent role on service-role write routes (GHSA-34q7-fv77-625j)

Fix merged in ArnasDon/wacrm PR #351 on 2026-07-08 — awaiting tagged release

https://github.com/ArnasDon/wacrm/pull/351
github Patch Available🟡 PoC Available

Service-role routes missing a role check (H3 + M2) · Advisory · ArnasDon/wacrm · GitHub

https://github.com/ArnasDon/wacrm/security/advisories/GHSA-34q7-fv77-625j

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 7× 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.

  1. 2026-09-20 20:16 UTCEPSS rescore
  2. 2026-09-19 19:44 UTCEG score recompute
  3. 2026-09-18 20:31 UTCEG score recompute
  4. 2026-09-18 19:59 UTCEG score recompute
  5. 2026-09-18 17:26 UTCEG score recompute
  6. 2026-09-18 16:54 UTCEG score recompute
  7. 2026-09-18 16:54 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-77239?
CVE-2026-77239 is a high vulnerability published on September 18, 2026. 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,…
When was CVE-2026-77239 disclosed?
CVE-2026-77239 was first published in the National Vulnerability Database on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-77239 actively exploited?
CVE-2026-77239 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 78.8% of all scored CVEs.
What is the CVSS score of CVE-2026-77239?
CVE-2026-77239 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-77239?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-77239, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-77239

Explore →

Is Your Infrastructure Affected by CVE-2026-77239?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs