Skip to content
Fencer Intel
medium 6.5

CVE-2013-4250 json

TYPO3 doesn't properly check file extensions

published 12y ago modified 4mo ago also GHSA-54jj-pxx2-pv8h , EUVD-2013-4153

cvss
6.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 67%
public exploits
0
none known

Summary

The (1) file upload component and (2) File Abstraction Layer (FAL) in TYPO3 6.0.x before 6.0.8 and 6.1.x before 6.1.3 do not properly check file extensions, which allow remote authenticated editors to execute arbitrary PHP code by uploading a .php file.

Patch / fix

  • packagist typo3/cms 6.0.8, 6.1.3

Is CVE-2013-4250 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.15% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 6.5 AV:N/AC:L/Au:S/C:P/I:P/A:P

Affected packages

ecosystem package affected fixed in
packagist typo3/cms
>=6.0.0, <6.0.8
>=6.1.0, <6.1.3
6.0.8
6.1.3

Classification

Weakness
  • CWE-20 Improper Input Validation
  • CWE-434 Unrestricted Upload of File with Dangerous Type

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.