Extension Typo3 Ai Integration Extension
Monthly
Any authenticated TYPO3 backend user can rewrite arbitrary page-record fields-including access permissions and configuration-when the AI Integration extension is active, because its backend write endpoint performs neither a permission check nor a field allowlist. The issue affects TYPO3 installations with typo3_ai_integration_extension installed and active and requires only a low-privileged backend session (CVSS 4.0 7.2 High; assessed CVSS 3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L). No public exploit code or CISA KEV entry was identified at time of analysis.
Exposure of a configured OpenAI API key in TYPO3 10 and 11 backend pages allows any authenticated backend user, including low-privilege editors, to retrieve the credential and use it at the site operator's expense. The issue affects installations of the TYPO3 AI Integration extension that have an API key configured; default installs without a key and unauthenticated or frontend-only users are not exposed. No public exploit was identified at time of analysis, and no CISA KEV entry was provided.
Any authenticated TYPO3 backend user can rewrite arbitrary page-record fields-including access permissions and configuration-when the AI Integration extension is active, because its backend write endpoint performs neither a permission check nor a field allowlist. The issue affects TYPO3 installations with typo3_ai_integration_extension installed and active and requires only a low-privileged backend session (CVSS 4.0 7.2 High; assessed CVSS 3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L). No public exploit code or CISA KEV entry was identified at time of analysis.
Exposure of a configured OpenAI API key in TYPO3 10 and 11 backend pages allows any authenticated backend user, including low-privilege editors, to retrieve the credential and use it at the site operator's expense. The issue affects installations of the TYPO3 AI Integration extension that have an API key configured; default installs without a key and unauthenticated or frontend-only users are not exposed. No public exploit was identified at time of analysis, and no CISA KEV entry was provided.