NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐘 Packagist
Not in CISA KEV

CVE-2010-5099 — cms

CVE-2010-5099 is a Improper Input Validation vulnerability in typo3/cms. 3 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for typo3/cms — see the affected versions and patch details below.

TYPO3 Path Traversal vulnerability

Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
3 known
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
3.1%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs88th percentile — riskier than 88% of all scored CVEsHighest risk
2.43%3.59%4.74%5.90%5.2%5.2%3.1%3.1%3.1%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

3 pkgs affected
🐘typo3/cms🐘typo3/cms🐘typo3/cms

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

The fileDenyPattern functionality in the PHP file inclusion protection API in TYPO3 4.2.x before 4.2.16, 4.3.x before 4.3.9, and 4.4.x before 4.4.5 does not properly filter file types, which allows remote attackers to bypass intended access restrictions and access arbitrary PHP files, as demonstrated using path traversal sequences with %00 null bytes and CVE-2010-3714 to read the TYPO3 encryption key from localconf.php.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagisttypo3/cms≥ 4.2.0&&< 4.2.164.2.16composer require typo3/cms:^4.2.16
🐘Packagisttypo3/cms≥ 4.3.0&&< 4.3.94.3.9composer require typo3/cms:^4.3.9
🐘Packagisttypo3/cms≥ 4.4.0&&< 4.4.54.4.5composer require typo3/cms:^4.4.5

Affected Products

1 product · 30 configurations
Application
typo3typo3
30 versions
4.2.04.2.14.2.24.2.34.2.44.2.54.2.64.2.74.2.84.2.94.2.104.2.11
Exploits & PoCs
3

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-15856webappsphp

TYPO3 - Arbitrary File Retrieval

by ikki · Dec 29, 2010

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update typo3/cms to 4.2.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2010-5099 is resolved across your whole dependency graph.

  3. Workarounds

    Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

The fileDenyPattern functionality in the PHP file inclusion protection API in TYPO3 4.2.x before 4.2.16, 4.3.x before 4.3.9, and 4.4.x before 4.4.5 does not properly filter file types, which allows remote attackers to bypass intended access restrictions and access arbitrary PHP files, as demonstrated using path traversal sequences with %00 null bytes and CVE-2010-3714 to read the TYPO3 encryption key from localconf.php.
O3 Security · Impact-Aware SCA

Is CVE-2010-5099 in your dependencies?

Find it across Packagist, including transitive dependencies.

CVE-2010-5099: cms Path Traversal — Fixed in 4.2.16