The frontend topic editing flow does not verify on the server side that the requesting visitor owns the topic being modified. As a result, a visitor who knows the identifier of a topic from the public forum can submit a modified update request for that topic directly and overwrite its content, without the application confirming ownership. Topic identifiers are visible in the public forum listing, and exploitation requires no privileged access or non-default configuration.
CVE-2026-77143
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 26, 2026
Advisory Details (1)
Auto-updated Aug 25, 2026TYPO3-EXT-SA-2026-021: Broken Access Control in extension "Forum" (pforum) - TYPO3 News
https://typo3.org/security/advisory/typo3-ext-sa-2026-021Vendor Advisories for CVE-2026-77143(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 20× in last 7d / 20× 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 03:27 UTCGHSA enrichment
- 2026-08-27 16:06 UTCEG score recompute
- 2026-08-27 16:06 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 04:43 UTCGHSA enrichment
- 2026-08-26 17:23 UTCGHSA enrichment
- 2026-08-26 15:59 UTCEG score recompute
- 2026-08-26 15:59 UTCGHSA enrichment
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-26 06:10 UTCEG score recompute
- 2026-08-26 06:10 UTCGHSA enrichment
- 2026-08-26 01:40 UTCGHSA enrichment
- 2026-08-25 14:21 UTCEG score recompute
- 2026-08-25 14:21 UTCGHSA enrichment
- 2026-08-25 14:15 UTCEG score recompute
- 2026-08-25 14:15 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
Related CVEs(same CWE)
Same CWE
10 shownCWE-862 · CWE-639
Frequently asked(5)
What is CVE-2026-77143?
When was CVE-2026-77143 disclosed?
Is CVE-2026-77143 actively exploited?
What is the CVSS score of CVE-2026-77143?
How do I remediate CVE-2026-77143?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-77143
Is Your Infrastructure Affected by CVE-2026-77143?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.