Skip to content

TYPO3 Allows Information Disclosure via DBAL Restriction Handling

Low severity GitHub Reviewed Published May 20, 2025 in TYPO3/typo3 • Updated May 20, 2025

Package

composer typo3/cms-core (Composer)

Affected versions

>= 9.0.0, <= 9.5.50
>= 10.0.0, <= 10.4.49
>= 11.0.0, <= 11.5.43
>= 12.0.0, <= 12.4.30
>= 13.0.0, <= 13.4.11

Patched versions

9.5.51
10.4.50
11.5.44
12.4.31
13.4.12

Description

Problem

When performing a database query involving multiple tables through the database abstraction layer (DBAL), frontend user permissions are only applied via FrontendGroupRestriction to the last table. As a result, data from additional tables included in the same query may be unintentionally exposed to unauthorized users.

Solution

Update to TYPO3 versions 9.5.51 ELTS, 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, 13.4.12 LTS that fix the problem described.

Credits

Thanks to Christian Futterlieb for reporting this issue, and to TYPO3 security team member Elias Häußler for fixing it.

References

@ohader ohader published to TYPO3/typo3 May 20, 2025
Published by the National Vulnerability Database May 20, 2025
Published to the GitHub Advisory Database May 20, 2025
Reviewed May 20, 2025
Last updated May 20, 2025

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(7th percentile)

Weaknesses

CVE ID

CVE-2025-47937

GHSA ID

GHSA-x8pv-fgxp-8v3x

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.