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.
Metrics
Affected Vendors & Products
Advisories
No advisories yet.
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
| Link | Providers |
|---|---|
| https://typo3.org/security/advisory/typo3-ext-sa-2026-035 |
|
History
Tue, 20 Oct 2026 12:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Sensitive Data Exposure in extension "TYPO3 AI Integration Extension" (ns_t3ai) | |
| Weaknesses | CWE-201 | |
| References |
| |
| Metrics |
cvssV4_0
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: TYPO3
Published:
Updated: 2026-10-20T09:30:44.456Z
Reserved: 2026-10-20T07:24:43.155Z
Link: CVE-2026-113459
No data.
Status : Received
Published: 2026-10-20T10:17:05.540
Modified: 2026-10-20T10:17:05.540
Link: CVE-2026-113459
No data.
OpenCVE Enrichment
No data.
Weaknesses