How severe is GHSA-wh8q-72cp-p5wf?

No CVSS score has been assigned to GHSA-wh8q-72cp-p5wf yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-wh8q-72cp-p5wf?

GHSA-wh8q-72cp-p5wf affects the following packages: typo3/cms (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-wh8q-72cp-p5wf?

Update typo3/cms to 6.2.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wh8q-72cp-p5wf is resolved across your whole dependency graph.

How do I detect GHSA-wh8q-72cp-p5wf 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-wh8q-72cp-p5wf if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is GHSA-wh8q-72cp-p5wf actively exploited in the wild?

No public exploit code has been indexed for GHSA-wh8q-72cp-p5wf 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-wh8q-72cp-p5wf published, and has it been updated?

GHSA-wh8q-72cp-p5wf was published on June 3, 2024 and was last updated on November 29, 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

Cross-Site Scripting in TYPO3 component Indexed SearchGHSA-wh8q-72cp-p5wf

GHSA-wh8q-72cp-p5wf is a security vulnerability in typo3/cms. A fix is available for typo3/cms — see the affected versions and patch details below.

Published

Jun 3, 2024

Updated

Nov 29, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 29, 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 encode editor input, the search result view of indexed_search is susceptible to Cross-Site Scripting, allowing authenticated editors to inject arbitrary HTML.

Affected Packages

1 total 1 fixed

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

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.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wh8q-72cp-p5wf is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

Failing to properly encode editor input, the search result view of indexed_search is susceptible to Cross-Site Scripting, allowing authenticated editors to inject arbitrary HTML.

O3 Security · Impact-Aware SCA

Is GHSA-wh8q-72cp-p5wf in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works