CVE-2026-113459
Sensitive Data Exposure in extension "TYPO3 AI Integration Extension" (ns_t3ai)
No known exploitation. EPSS puts it in the 29th percentile. Fixed in 14.0.2.
What to do
Find your product and version, then upgrade to the build on the right.
- TYPO3 Extension "TYPO3 AI Integration Extension"Affected: < 14.0.2Upgrade to: 14.0.2Stated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
In versions running on TYPO3 10 and 11, the configured OpenAI API key is embedded in every backend page, so that the editor plugin can contact the OpenAI service directly from the browser. Any authenticated backend user can read the key and use it at the expense of the site operator. This only applies if an API key has been configured.
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.4% chance of exploitation activity in the next 30 days, which ranks it in the 29th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
4 events over 0 days, from the signal feeds we watch.
- Publishedweakness classified, record updated, record updated
Affected products
Technical detail
Weaknesses
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 TYPO3, 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