How severe is GHSA-p5c5-gmj4-g48f?

No CVSS score has been assigned to GHSA-p5c5-gmj4-g48f yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-p5c5-gmj4-g48f?

GHSA-p5c5-gmj4-g48f affects the following packages: typo3/cms (Packagist), typo3/cms (Packagist), typo3/cms (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-p5c5-gmj4-g48f?

Update typo3/cms to 6.2.26 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p5c5-gmj4-g48f is resolved across your whole dependency graph.

How do I detect GHSA-p5c5-gmj4-g48f 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-p5c5-gmj4-g48f 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.

How does O3 Security protect against GHSA-p5c5-gmj4-g48f?

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

Is GHSA-p5c5-gmj4-g48f actively exploited in the wild?

No public exploit code has been indexed for GHSA-p5c5-gmj4-g48f 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-p5c5-gmj4-g48f published, and has it been updated?

GHSA-p5c5-gmj4-g48f was published on June 5, 2024 and was last updated on December 2, 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

GHSA-p5c5-gmj4-g48f — typo3/cms

GHSA-p5c5-gmj4-g48f is a security vulnerability in typo3/cms. A fix is available for typo3/cms — see the affected versions and patch details below.

Cross-Site Scripting (XSS) vulnerability in typolinks

Published

Jun 5, 2024

Updated

Dec 2, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Dec 2, 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

All link fields within the TYPO3 installation are vulnerable to Cross-Site Scripting as authorized editors can insert data commands by using the url scheme "data:".

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`typo3/cms`	≥ 6.2.0&&< 6.2.26	6.2.26`composer require typo3/cms:^6.2.26`
🐘Packagist	`typo3/cms`	≥ 7.6.0&&< 7.6.10	7.6.10`composer require typo3/cms:^7.6.10`
🐘Packagist	`typo3/cms`	≥ 8.0.0&&< 8.2.1	8.2.1`composer require typo3/cms:^8.2.1`

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.26 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p5c5-gmj4-g48f 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-p5c5-gmj4-g48f can be triaged on real exposure rather than presence alone.

Tailored to GHSA-p5c5-gmj4-g48f. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

All link fields within the TYPO3 installation are vulnerable to Cross-Site Scripting as authorized editors can insert data commands by using the url scheme "data:".

O3 Security · Impact-Aware SCA

Is GHSA-p5c5-gmj4-g48f in your dependencies?

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

Scan my dependencies How O3 SCA works