CVE-2026-49741: TYPO3 CMS - Privilege Escalation & SQL Injection in Form Framework

Published Jun 9, 2026
·
Updated

Problem Backend users with write access to the formdefinition 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.

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

Other sources

Backend users with write access to the formdefinition 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.

MITRE

Backend users with write access to the formdefinition 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.3.

NVD

Affected Software

3 affected componentsFixes available
Typo3 TYPO3 CMS>=14.0.0<=14.3.3
composer/typo3/cms-form>=14.0.0<14.3.3
14.3.3
composer/typo3/cms-core>=14.0.0<14.3.3
14.3.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/typo3/cms-form to a version that resolves this vulnerability.

    Fixed in 14.3.3
  2. Upgrade

    Upgrade composer/typo3/cms-core to a version that resolves this vulnerability.

    Fixed in 14.3.3
  3. Upgrade

    Upgrade TYPO3 CMS to a version that resolves this vulnerability.

    Fixed in 14.3.3Patch TYPO3-CORE-SA-2026-017

Event History

Jun 9, 2026
CVE Published
via MITRE·10:54 AM
Data Sourced
via MITRE·10:54 AM
DescriptionWeakness
Data Sourced
via NVD·11:16 AM
DescriptionSeverityWeakness
Jun 12, 2026
Advisory Published
via GitHub·07:32 PM
Data Sourced
via GitHub·07:32 PM
DescriptionWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-49741?

CVE-2026-49741 has a severity rating of high with a CVSS score of 8.7.

2

How do I fix CVE-2026-49741?

To mitigate CVE-2026-49741, ensure that your Typo3 CMS is updated to the latest version that addresses this vulnerability.

3

What type of vulnerability is CVE-2026-49741?

CVE-2026-49741 is a privilege escalation and SQL injection vulnerability.

4

Who is affected by CVE-2026-49741?

Backend users of Typo3 CMS with write access to the form_definition database table are affected by CVE-2026-49741.

5

What can attackers achieve with CVE-2026-49741?

Attackers can use CVE-2026-49741 to inject arbitrary form configurations and bypass permission checks.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203