Executive Summary

This vulnerability affects TYPO3 CMS versions 14.0.0 to 14.3.3 and involves backend users who have write access to the form_definition database table. These users could bypass the Form Framework's persistence validation and permission checks by using DataHandler to directly create, update, or delete form definition records. This bypass allowed them to inject arbitrary form configurations, which reintroduced attack vectors such as SQL injection and privilege escalation that were previously addressed in an earlier TYPO3 security advisory.

Useful 0 Not Useful 0

Impact Analysis

The vulnerability can lead to serious security impacts including privilege escalation and SQL injection attacks. An attacker with backend write access could manipulate form definitions to execute unauthorized database queries or escalate their privileges within the TYPO3 CMS environment. This could compromise the integrity and confidentiality of the system, potentially allowing unauthorized access to sensitive data or control over the CMS.

Useful 0 Not Useful 0

Detection Guidance

Detection of this vulnerability involves checking for unauthorized or suspicious modifications to the form_definition database table by backend users with write access. Since the vulnerability allows bypassing validation and permission checks via DataHandler, monitoring database changes and DataHandler operations related to form definitions is crucial.

Specifically, you can audit logs for DataHandler operations that create, update, or delete records in the form_definition table without proper validation tokens (HMAC-SHA3-384). Look for error logs generated by the FormDefinitionDataHandlerHook that nullifies unauthorized operations.

Suggested commands include:

• Query the form_definition table for recent changes: `SELECT * FROM form_definition WHERE tstamp > NOW() - INTERVAL '1 DAY';`
• Check TYPO3 system logs for DataHandler errors related to form_definition modifications.
• If you have shell access, use grep to find suspicious DataHandler invocations or error messages in log files, e.g., `grep -i 'form_definition' /path/to/typo3/logs/*`

Additionally, verify the TYPO3 version to ensure it is updated to 14.3.3 or later, as earlier versions are vulnerable.

Useful 0 Not Useful 0

Mitigation Strategies

The primary immediate mitigation step is to update TYPO3 CMS to version 14.3.3 LTS or later, where this vulnerability is fixed.

This update includes the implementation of the FormDefinitionPersistenceGuard service, which enforces strict validation and permission checks on create, update, and delete operations on the form_definition table, preventing unauthorized DataHandler operations.

Additionally, review backend user permissions to ensure that only trusted users have write access to the form_definition table.

Follow the TYPO3 Security Guide and subscribe to the typo3-announce mailing list for ongoing updates and security advisories.

Useful 0 Not Useful 0