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.
Published: 2026-10-20
Score: 7.1 High
EPSS: < 1% Very Low
KEV: No
Impact: Sensitive Data Exposure
Action: Apply Patch
AI Analysis

Impact

In TYPO3 10 and 11, the extension that integrates OpenAI embeds the configured API key within every backend page so the editor can call the service directly from the browser. Any authenticated administrator or editor can view the page source and capture the key, allowing them to use the OpenAI service at the operator’s expense. The vulnerability does not allow arbitrary code execution but leaks a credential that can be abused for unauthorized use, increasing costs and potentially violating privacy or contractual constraints.

Affected Systems

TYPO3 systems running Extension "TYPO3 AI Integration Extension" on versions 10 or 11 are affected whenever a personal OpenAI API key has been entered in the extension configuration. No other TYPO3 versions or extensions are listed as vulnerable.

Risk and Exploitability

The CVSS score of 7.1 indicates a medium‑to‑high severity of data exposure. The EPSS score of less than 1% suggests that exploitation is currently rare, and the vulnerability is not listed in the CISA KEV catalog. An attacker must be an authenticated backend user with access to the configuration pages; once the key is exposed, it can be used immediately. The impact is confined to credential leakage rather than service disruption, but the cost and reputational risks can be significant if the key is abused.

Generated by OpenCVE AI on October 20, 2026 at 15:22 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the TYPO3 AI Integration Extension to the latest patched release that removes the API key from page output.
  • If an update is not possible, delete the configured OpenAI API key from the extension settings or ensure it is stored in a secure, non‑disclosed location.
  • Limit backend user roles that can view or edit the OpenAI configuration, restricting exposure to only those who require it for their workflow.

Generated by OpenCVE AI on October 20, 2026 at 15:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 21 Oct 2026 17:15:00 +0000

Type Values Removed Values Added
First Time appeared Typo3
Typo3 extension Typo3 Ai Integration Extension
Vendors & Products Typo3
Typo3 extension Typo3 Ai Integration Extension

Tue, 20 Oct 2026 16:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


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

{'score': 7.1, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N'}


Subscriptions

Typo3 Extension Typo3 Ai Integration Extension
cve-icon MITRE

Status: PUBLISHED

Assigner: TYPO3

Published:

Updated: 2026-10-20T15:48:56.323Z

Reserved: 2026-10-20T07:24:43.155Z

Link: CVE-2026-113459

cve-icon Vulnrichment

Updated: 2026-10-20T15:48:48.256Z

cve-icon NVD

Status : Deferred

Published: 2026-10-20T10:17:05.540

Modified: 2026-10-20T19:28:52.970

Link: CVE-2026-113459

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-21T16:46:06Z

Weaknesses
  • CWE-201

    Insertion of Sensitive Information Into Sent Data