The extension resolves the targeted club record from a user-supplied request argument in its frontend edit, update, and activate actions, but performs no ownership check in any of them. An unauthenticated visitor who knows the UID of a club record can send a direct request to the update or activate action and overwrite that record, or publish one still awaiting approval, without owning it.
CVE-2026-77141
This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 85% 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
- 8.8
- EG Score
- 8.8(medium)
- EG Risk
- 55(Track)EG Risk 55/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 computedSeverity88% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 15%
- KEV
- Not listed
Published
August 25, 2026
Last Modified
August 27, 2026
Advisory Details (1)
Auto-updated Aug 25, 2026TYPO3-EXT-SA-2026-019: Broken Access Control in extension "Club Directory" (clubdirectory) - TYPO3 News
https://typo3.org/security/advisory/typo3-ext-sa-2026-019Vendor Advisories for CVE-2026-77141(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 21× in last 7d / 21× 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-08-28 07:31 UTCEG score recompute
- 2026-08-28 07:31 UTCGHSA enrichment
- 2026-08-27 20:20 UTCEG score recompute
- 2026-08-27 20:20 UTCGHSA enrichment
- 2026-08-27 15:42 UTCEG score recompute
- 2026-08-27 15:42 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 04:32 UTCGHSA enrichment
- 2026-08-26 17:23 UTCEG score recompute
- 2026-08-26 17:23 UTCGHSA enrichment
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-26 13:40 UTCGHSA enrichment
- 2026-08-26 02:31 UTCGHSA enrichment
- 2026-08-25 15:22 UTCEG score recompute
- 2026-08-25 15:22 UTCGHSA enrichment
- 2026-08-25 14:56 UTCEG score recompute
- 2026-08-25 14:56 UTCGHSA enrichment
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 09:22 UTCEG score recompute
- 2026-08-25 09:07 UTCEG score recompute
- 2026-08-25 09:06 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-77141?
When was CVE-2026-77141 disclosed?
Is CVE-2026-77141 actively exploited?
What is the CVSS score of CVE-2026-77141?
How do I remediate CVE-2026-77141?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-77141
Is Your Infrastructure Affected by CVE-2026-77141?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.