---
id: "CVE-2026-113459"
kind: "vulnerability"
aliases: ["CVE-2026-113459"]
title: "TYPO3: OpenAI API key exposed in every backend page source"
severity: "high"
cvss: 7.1
epss: null
exploited: false
status: "open"
category: "ai-tooling"
products: []
ecosystems: []
tags: ["ai-tooling", "openai", "php", "self-hosted", "typo3"]
not_affected_if: ["backend-access-restricted", "no-api-key-configured", "typo3-12-or-newer"]
published_at: "2026-10-20T10:17:05+00:00"
first_seen_at: "2026-10-23T21:57:20+00:00"
updated_at: "2026-10-25T03:34:44+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-113459", "first_seen_at": "2026-10-23T21:57:20+00:00"}]
---

# TYPO3: OpenAI API key exposed in every backend page source

On TYPO3 versions 10 and 11, a configured OpenAI API key is embedded in each backend page so the editor plugin can call OpenAI from the browser. Any logged-in backend user can read the key and spend the site operator's OpenAI credits.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check whether an OpenAI API key is configured in the TYPO3 extension or site settings for the AI editor plugin.
- Inspect the page source of a TYPO3 backend page as a backend user and search for the key prefix `sk-`.
- Confirm the installed TYPO3 major version is `10` or `11`.

## Fix

- unknown

## Timeline

- 2026-10-23T21:57:20+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-113459

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_