Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
MEDIUM severity

GHSA-g7hw-jh4p-75wr typo3/cms

MEDIUMFix: TYPO3/typo3@044d7db

GHSA-g7hw-jh4p-75wr is a medium-severity (CVSS 6.1) vulnerability in typo3/cms. A fix is available for typo3/cms — see the affected versions and patch details below.

TYPO3 Cross-Site Scripting in Filelist Module

Published
Jun 7, 2024
Updated
Dec 4, 2024
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Dec 4, 2024 · OSV.dev, 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

It has been discovered that the output table listing in the “Files” backend module is vulnerable to cross-site scripting when a file extension contains malicious sequences.

Access to the file system of the server - either directly or through synchronization - is required to exploit the vulnerability.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagisttypo3/cms10.0.0&&< 10.2.110.2.1composer require typo3/cms:^10.2.1
🐘Packagisttypo3/cms8.0.0&&< 8.7.308.7.30composer require typo3/cms:^8.7.30
🐘Packagisttypo3/cms9.0.0&&< 9.5.129.5.12composer require typo3/cms:^9.5.12

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 10.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g7hw-jh4p-75wr is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-g7hw-jh4p-75wr can be triaged on real exposure rather than presence alone.

Tailored to GHSA-g7hw-jh4p-75wr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

It has been discovered that the output table listing in the “Files” backend module is vulnerable to cross-site scripting when a file extension contains malicious sequences. Access to the file system of the server - either directly or through synchronization - is required to exploit the vulnerability.
O3 Security · Impact-Aware SCA

Is GHSA-g7hw-jh4p-75wr in your dependencies?

O3 Security finds GHSA-g7hw-jh4p-75wr across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-g7hw-jh4p-75wr: XSS (Medium 6.1) | O3 Security