Christian Kuhn

The backend module for reviewing consent history fails to validate sorting, grouping, and index options received in requests before using them in a database query. While filter conditions are bound as parameters, the lack of validation for other options allows a backend user with access to history or statistics functions to perform unauthorized reads of arbitrary database data, including password hashes for both backend and frontend users.

The software embeds the correct answer to each CAPTCHA within the image data of the CAPTCHA itself. This occurs in the default configuration because the audio feature, which triggers the embedding of the answer, is enabled by default. Consequently, any entity capable of requesting a CAPTCHA image can extract the answer and submit it, allowing automated clients to bypass the challenge. Forms that utilize this CAPTCHA as the sole defense against automated submissions are susceptible to bot abuse.

An authenticated, low-privileged backend user can exploit a backend AJAX endpoint used for inline editing that fails to restrict access to fields the user is not permitted to see or edit. By supplying arbitrary table, field, and record parameters, an attacker can trigger an error response that discloses the current database value of the requested field. This can lead to the exposure of sensitive information, including password hashes for both backend and frontend users. Exploitation requires a valid account with access to the extensions backend module.

An authenticated backend user with access to the Mask module can perform path traversal, a technique used to access files and directories that are restricted from the user. The extension fails to validate a client-supplied template element key used to build file paths for saving and deleting Mask template files. By supplying a key containing path traversal sequences, an attacker can create or delete .html files outside the configured template directory.

The extension fails to properly sanitize user input before using it in a database query. This allows an unauthenticated attacker to perform SQL injection, which is the insertion of malicious SQL code into a query, through a URL parameter on pages utilizing the "Date Menu of news articles" plugin. This issue is exploitable when the "Date Menu of news articles" plugin is active and the TypoScript/Plugin setting `disableOverrideDemand` is not enabled.

The issue concerns password hashes being reflected in the editing forms of the TYPO3 backend user interface, allowing attackers to crack the plaintext password using brute force techniques. Exploiting this issue requires a valid backend user account.