CVE-2026-49741
highpriority · track · 0OT risk · elevatedEPSS 0.002 · 16 %ileDEEUUSEPSS · scored 2026-10-27
Backend users with write access to the form_definition database table were able to directly create, update, or delete form definition records via DataHandler, bypassing the Form Framework's persistence validation and permission checks. This allowed injecting arbitrary form configurations, re-enabling attack vectors originally addressed in TYPO3-CORE-SA-2018-003, including SQL injection and privilege escalation. This issue affects TYPO3 CMS versions 14.0.0-14.3.2.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · medium–high · 6.2–8.7
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (13)
Products and version ranges known to be affected.
advisories (2)
Vendor and ecosystem advisories describing this.
- WID-SEC-W-2026-1835TYPO3 Core: Mehrere SchwachstellenDeutsch2026-06-08csaf · cert_bundDE
Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in TYPO3 Core ausnutzen, um Sicherheitsbeschränkungen zu umgehen, Benutzer auf schädliche Websites umzuleiten, beliebigen Code auszuführen, Berechtigungen zu eskalieren oder andere Auswirkungen zu verursachen.
- GHSA-jh32-v29g-68pqTYPO3 CMS has Privilege Escalation & SQL Injection in its Form Framework2026-06-12ghsa · osvUS
### Problem Backend users with write access to the `form_definition` database table were able to directly create, update, or delete form definition records via `DataHandler`, bypassing the Form Framework's persistence validation and permission checks. This allowed injecting arbitrary form configurations, re-enabling attack vectors originally addressed in [TYPO3-CORE-SA-2018-003](https://typo3.org/security/advisory/typo3-core-sa-2018-003), including SQL injection and privilege escalation. ### Solution Update to TYPO3 version 14.3.3 LTS that fixes the problem described. ### Credits TYPO3 CMS thanks Selçuk Güney for reporting this issue, and to TYPO3 core & security team member Oliver Hader for fixing it. ### Resources * [TYPO3-CORE-SA-2026-017](https://typo3.org/security/advisory/typo3-core-sa-2026-017)
also known as (3)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (9)
External citations — patches, advisories, analysis.
- https://access.redhat.com/security/cve/cve-2026-49741cnnvd
- https://nvd.nist.gov/vuln/detail/CVE-2026-49741cnnvd
- https://typo3.org/security/advisory/typo3-core-sa-2018-003Patchcnnvd
- https://github.com/TYPO3/typo3/commit/c90493c13b633f328cf2c066182c90a1655ff0fcenisa_euvd
- https://typo3.org/security/advisory/typo3-core-sa-2018-003enisa_euvd
- https://typo3.org/security/advisory/typo3-core-sa-2026-017enisa_euvd
- https://github.com/TYPO3/typo3/commit/c90493c13b633f328cf2c066182c90a1655ff0fcnvd
- https://typo3.org/security/advisory/typo3-core-sa-2018-003nvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan