How severe is GHSA-wrpf-2x8h-82gr?

No CVSS score has been assigned to GHSA-wrpf-2x8h-82gr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-wrpf-2x8h-82gr?

GHSA-wrpf-2x8h-82gr affects the following packages: typo3/cms (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-wrpf-2x8h-82gr?

Update typo3/cms to 6.2.20 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wrpf-2x8h-82gr is resolved across your whole dependency graph.

How do I detect GHSA-wrpf-2x8h-82gr in my Packagist dependencies?

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.

How do I mitigate GHSA-wrpf-2x8h-82gr if there is no patch (or I can't update yet)?

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.

Is GHSA-wrpf-2x8h-82gr actively exploited in the wild?

No public exploit code has been indexed for GHSA-wrpf-2x8h-82gr yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-wrpf-2x8h-82gr published, and has it been updated?

GHSA-wrpf-2x8h-82gr was published on June 4, 2024 and was last updated on December 1, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

Typo3 Arbitrary File Disclosure in Form ComponentGHSA-wrpf-2x8h-82gr

GHSA-wrpf-2x8h-82gr is a security vulnerability in typo3/cms. A fix is available for typo3/cms — see the affected versions and patch details below.

Published

Jun 4, 2024

Updated

Dec 1, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 1, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐘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

Failing to properly validate user input, the form component is susceptible to Arbitrary File Disclosure. A valid backend user account is needed to exploit this vulnerability. Only forms are vulnerable, which contain upload fields.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`typo3/cms`	≥ 6.2.0&&< 6.2.20	6.2.20`composer require typo3/cms:^6.2.20`

Detection & mitigation playbook

Open-source dependency

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.
Fix
Update typo3/cms to 6.2.20 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wrpf-2x8h-82gr is resolved across your whole dependency graph.
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.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-wrpf-2x8h-82gr in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works