CVE-2013-4250: TYPO3 doesn't properly check file extensions

CVE-2013-4250 · Severity: medium · CVSS 4 · Published 2022-05-17

TYPO3 doesn't properly check file extensions

Technologies: typo3/cms (Packagist). Vendors: Packagist.

Quick answers

Is CVE-2013-4250 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2013-4250 being exploited in the wild.
How severe is CVE-2013-4250?
Medium severity, with a CVSS score of 4, published 17 May 2022.
Which products and versions are affected?
typo3/cms (Packagist) ECOSYSTEM:introduced=6.0.0,fixed=6.0.8.
Is there a fix for CVE-2013-4250?
Yes. typo3/cms (Packagist): upgrade to 6.0.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2013-4250?
Check whether you run typo3/cms (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • typo3/cms (Packagist): upgrade to 6.0.8 or later
    composer require typo3/cms:^6.0.8

Affected products

  • typo3/cms (Packagist) ECOSYSTEM:introduced=6.0.0,fixed=6.0.8

Identifiers

  • CVE-2013-4250
  • GHSA-54jj-pxx2-pv8h

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.