CVE-2026-49738

TYPO3 CMS - Broken Access Control in File Abstraction Layer

Published Jun 9, 2026 CVSS 4.0 · 2.1 Low EPSS < 1% KEV · Not listed
Description
The path allowance check in GeneralUtility::isAllowedAbsPath() performed a plain string prefix comparison without requiring a directory separator boundary, causing a path like /var/www/html-other/secret.yaml to be incorrectly accepted as valid when the project root was /var/www/html. Administrator users with access to the File Abstraction Layer were able to create new file storage definitions pointing to directories outside the project root, bypassing this path check. This issue affects TYPO3 CMS versions before 10.4.57, 11.0.0-11.5.50, 12.0.0-12.4.45, 13.0.0-13.4.30 and 14.0.0-14.3.2.

Analysis

AI-generated

Technical impact

The path allowance check in GeneralUtility::isAllowedAbsPath() performs a plain string prefix comparison without requiring a directory separator boundary. This flaw causes a path such as /var/www/html‑other/secret.yaml to be incorrectly accepted as valid when the project root is /var/www/html. Administrator users that have access to the File Abstraction Layer can create new file storage definitions pointing to directories outside the project root, bypassing the path validation. The flaw affects TYPO3 CMS versions before 10.4.57, 11.0.0‑11.5.50, 12.0.0‑12.4.45, 13.0.0‑13.4.30 and 14.0.0‑14.3.2.

Affected Systems

TYPO3 CMS versions before 10.4.57, 11.0.0–11.5.50, 12.0.0–12.4.45, 13.0.0–13.4.30, and 14.0.0–14.3.2 are vulnerable.

Risk and Exploitability

The CVSS score of 2.1 indicates a low severity from a technical perspective. Because the vulnerability is only exploitable by users who already have administrative access to the File Abstraction Layer, the risk is limited to environments where an attacker can compromise an administrator account. The EPSS score is less than 1% and the issue is not listed in the CISA KEV catalog, suggesting that widespread exploitation has not been observed. Nevertheless, the bug permits an attacker with the required privileges to access or alter files outside the designated project root.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade TYPO3 CMS to a fixed version (at least 10.4.57, 11.5.50, 12.4.45, 13.4.30, or 14.3.2).
  • If an immediate upgrade is not possible, restrict access to the File Abstraction Layer to trusted administrators and review existing storage definitions for paths outside the project root.
  • Remove or correct any storage definitions that point to directories outside the intended project root to prevent unintended file access.

Generated by OpenCVE AI on July 30, 2026 at 00:11 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-jf56-v8jc-jcc5 TYPO3 CMS has Broken Access Control in its File Abstraction Layer
History
Type Values Removed Values Added
Description The path allowance check in GeneralUtility::isAllowedAbsPath() performed a plain string prefix comparison without requiring a directory separator boundary, causing a path like /var/www/html-other/secret.yaml to be incorrectly accepted as valid when the project root was /var/www/html. Administrator users with access to the File Abstraction Layer were able to create new file storage definitions pointing to directories outside the project root, bypassing this path check. This issue affects TYPO3 CMS versions before 10.4.57, 11.0.0-11.5.51, 12.0.0-12.4.46, 13.0.0-13.4.31 and 14.0.0-14.3.3. The path allowance check in GeneralUtility::isAllowedAbsPath() performed a plain string prefix comparison without requiring a directory separator boundary, causing a path like /var/www/html-other/secret.yaml to be incorrectly accepted as valid when the project root was /var/www/html. Administrator users with access to the File Abstraction Layer were able to create new file storage definitions pointing to directories outside the project root, bypassing this path check. This issue affects TYPO3 CMS versions before 10.4.57, 11.0.0-11.5.50, 12.0.0-12.4.45, 13.0.0-13.4.30 and 14.0.0-14.3.2.
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description The path allowance check in GeneralUtility::isAllowedAbsPath() performed a plain string prefix comparison without requiring a directory separator boundary, causing a path like /var/www/html-other/secret.yaml to be incorrectly accepted as valid when the project root was /var/www/html. Administrator users with access to the File Abstraction Layer were able to create new file storage definitions pointing to directories outside the project root, bypassing this path check. This issue affects TYPO3 CMS versions before 10.4.57, 11.0.0-11.5.51, 12.0.0-12.4.46, 13.0.0-13.4.31 and 14.0.0-14.3.3.
Title TYPO3 CMS - Broken Access Control in File Abstraction Layer
First Time appeared Typo3
Typo3 typo3
Weaknesses CWE-22
CPEs cpe:2.3:a:typo3:typo3:*:*:*:*:*:*:*:*
Vendors & Products Typo3
Typo3 typo3
References
Metrics cvssV4_0

{'score': 2.1, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-22

    Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Sources

Status
PUBLISHED
Assigner
TYPO3
Published
Updated
Jul 15, 2026, 12:48 PM
Reserved
Jun 1, 2026, 10:52 AM
Status
Deferred
Published
Jun 9, 2026, 11:16 AM
Modified
Jul 23, 2026, 8:10 AM