Summary
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, including SQL injection and privilege escalation.
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
Impact
Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Update to TYPO3 version 14.3.3 LTS that fixes the problem described.
Frequently Asked Questions
- What is CVE-2026-49741? CVE-2026-49741 is a high-severity SQL injection vulnerability in typo3/cms-core (composer), affecting versions >= 14.0.0, < 14.3.3. It is fixed in 14.3.3. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
- Which packages are affected by CVE-2026-49741?
typo3/cms-core(composer) (versions >= 14.0.0, < 14.3.3)typo3/cms-form(composer) (versions >= 14.0.0, < 14.3.3)
- Is there a fix for CVE-2026-49741? Yes. CVE-2026-49741 is fixed in 14.3.3. Upgrade to this version or later.
- Is CVE-2026-49741 exploitable, and should I be worried? Whether CVE-2026-49741 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-49741 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-49741?
- Upgrade
typo3/cms-coreto 14.3.3 or later - Upgrade
typo3/cms-formto 14.3.3 or later
- Upgrade