Path Traversal in TYPO3 File Abstraction Layer Storages

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.5 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:N

EPSS

• CVE-2023-30451: 1.16% estimated exploitation activity in the next 30 days; percentile 67.19 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Problem Configurable storages using the local driver of the File Abstraction Layer (FAL) could be configured to access directories outside of the root directory of the corresponding project. The system setting in BE/lockRootPath was not evaluated by the file abstraction layer component. An administrator-level backend user account is required to exploit this vulnerability. Solution Update to TYPO3 versions 8.7.57 ELTS, 9.5.46 ELTS, 10.4.43 ELTS, 11.5.35 LTS, 12.4.11 LTS, 13.0.1 that fix the problem described. ℹ️ Strong security defaults - Manual actions required see Important: #102800 changelog Assuming that a web project is located in the directory /var/www/example.org (the "project root path" for Composer-based projects) and the publicly accessible directory is located at /var/www/example.org/public (the "public root path"), accessing resources via the File Abstraction Layer component is limited to the mentioned directories. To grant additional access to directories, they must be…

Published by the source

13 Feb 2024, 19:08 UTC

Last modified by the source

20 Feb 2024, 15:17 UTC

Source last checked

26 Oct 2026, 14:18 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-w6x2-jg8h-p6mp

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-30451

Advisory: Path Traversal in TYPO3 File Abstraction Layer Storages
IDs: CVE-2023-30451, GHSA-w6x2-jg8h-p6mp
Record: https://patchnext.com/advisories/cve-2023-30451 (revision 1, source checked 26 Oct 2026, 14:18 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: typo3/cms-core 13.0.1, 12.4.11, 11.5.35, 10.4.43, 9.5.46, 8.7.57. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist typo3/cms-core: affected >= 8.0.0, <= 8.7.56; >= 9.0.0, <= 9.5.45; >= 10.0.0, <= 10.4.42; >= 11.0.0, <= 11.5.34; >= 12.0.0, <= 12.4.10; >= 13.0.0, <= 13.0.0; fixed in 8.7.57, 12.4.11, 9.5.46, 10.4.43, 11.5.35, 13.0.1

## Suggested inspection (read-only)
- Packagist typo3/cms-core: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on typo3/cms-core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-w6x2-jg8h-p6mp (GitHub-reviewed advisory GHSA-w6x2-jg8h-p6mp lists affected ranges: Packagist typo3/cms-core >=8.0.0 =9.0.0 =10.0.0 =11.0.0 =12.0.0 =13.0.0 <=13.0.0)

Commands are suggestions: review each one before running it.