CVE-2026-77203

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-26. A secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.8Exploit: None knownExposed services: Not assessed

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

The Groups – Memberships and Access Control plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 4.6.0. This is due to the groups_join() function deriving group-join eligibility from the ambient post's author capabilities via the global $post->post_author rather than from the currently authenticated user's own capabilities, while simultaneously minting and returning a valid groups-join-data hash and WordPress nonce for the caller in the same response — eliminating all authorization barriers to self-enrollment. This makes it possible for authenticated attackers, with Subscriber-level access and above, to enroll themselves into any group including privileged groups carrying the groups_admin_groups capability, and to subsequently create and join a group containing every registered WordPress capability, effectively escalating their privileges to Administrator. Exploitation requires the attacker to supply an Administrator-authored post ID via the post_ID parameter of the authenticated wp_ajax_parse_media_shortcode handler in order to establish the privileged ambient post context used by the flawed authorization check.

CVSS v3
8.8
EG Score
8.8HIGHhigh confidence
EG Risk
40
EG Risk 40/100CISA SSVC

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
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
23rd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 26, 2026

Last Modified

September 28, 2026

Vendor Advisories for CVE-2026-77203(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 26× in last 7d / 37× 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-10-04 23:22 UTCEPSS rescore
  2. 2026-10-04 23:10 UTCGHSA enrichment
  3. 2026-10-04 10:33 UTCGHSA enrichment
  4. 2026-10-03 21:55 UTCEG score recompute
  5. 2026-10-03 21:55 UTCGHSA enrichment
  6. 2026-10-03 14:26 UTCEPSS rescore
  7. 2026-10-03 09:08 UTCGHSA enrichment
  8. 2026-10-02 20:30 UTCEG score recompute
  9. 2026-10-02 20:30 UTCGHSA enrichment
  10. 2026-10-02 07:51 UTCEG score recompute
  11. 2026-10-02 07:51 UTCGHSA enrichment
  12. 2026-10-01 19:50 UTCEPSS rescore
  13. 2026-10-01 19:14 UTCGHSA enrichment
  14. 2026-10-01 06:35 UTCGHSA enrichment
  15. 2026-09-30 17:59 UTCEG score recompute
  16. 2026-09-30 17:59 UTCGHSA enrichment
  17. 2026-09-30 05:22 UTCGHSA enrichment
  18. 2026-09-29 16:46 UTCEG score recompute
  19. 2026-09-29 16:46 UTCGHSA enrichment
  20. 2026-09-29 15:24 UTCEPSS rescore
  21. 2026-09-29 04:04 UTCEG score recompute
  22. 2026-09-29 04:04 UTCGHSA enrichment
  23. 2026-09-28 15:26 UTCEG score recompute
  24. 2026-09-28 15:26 UTCGHSA enrichment
  25. 2026-09-28 13:52 UTCEPSS rescore
Show 12 more
  1. 2026-09-28 13:15 UTCGHSA enrichment
  2. 2026-09-28 00:39 UTCEG score recompute
  3. 2026-09-28 00:39 UTCGHSA enrichment
  4. 2026-09-27 13:48 UTCEPSS rescore
  5. 2026-09-27 12:02 UTCGHSA enrichment
  6. 2026-09-26 23:26 UTCEG score recompute
  7. 2026-09-26 23:25 UTCGHSA enrichment
  8. 2026-09-26 22:54 UTCEG score recompute
  9. 2026-09-26 22:54 UTCGHSA enrichment
  10. 2026-09-26 18:21 UTCEG score recompute
  11. 2026-09-26 17:38 UTCEG score recompute
  12. 2026-09-26 17:34 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-77203?
CVE-2026-77203 is a high vulnerability published on September 26, 2026. The Groups – Memberships and Access Control plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 4.6.0. This is due to the groupsjoin() function deriving group-join eligibility from the ambient post's author capabilities via the global $post->postauthor…
When was CVE-2026-77203 disclosed?
CVE-2026-77203 was first published on September 26, 2026, with the most recent update on September 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-77203 actively exploited?
CVE-2026-77203 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-77203?
CVE-2026-77203 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-77203?
No fix for CVE-2026-77203 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-77203 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-77203?

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