CVE-2026-112070
Broken Access Control in extension "Analytics" (analytics)
No known exploitation. EPSS puts it in the 25th percentile. Fixed in 1.1.1.
What to do
Find your product and version, then upgrade to the build on the right.
- TYPO3 Extension "Analytics"Affected: < 1.1.1Upgrade to: 1.1.1Stated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
The AJAX routes of the extension do not check whether a backend user has access to the related module or dashboard widget. Any backend user can therefore retrieve analytics data of the sites they have page access to.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.3% chance of exploitation activity in the next 30 days, which ranks it in the 25th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
5 events over 0 days, from the signal feeds we watch.
- Publishedweakness classified, att&ck mapped, record updated, record updated
Affected products
Technical detail
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
Sources
References in the record
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Extension "Analytics", not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI