How severe is GHSA-8j9v-4hhh-x43c?

No CVSS score has been assigned to GHSA-8j9v-4hhh-x43c yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-8j9v-4hhh-x43c?

GHSA-8j9v-4hhh-x43c affects the following packages: typo3/cms (Packagist), typo3/cms (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-8j9v-4hhh-x43c?

Update typo3/cms to 6.2.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8j9v-4hhh-x43c is resolved across your whole dependency graph.

How do I detect GHSA-8j9v-4hhh-x43c 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-8j9v-4hhh-x43c 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-8j9v-4hhh-x43c actively exploited in the wild?

No public exploit code has been indexed for GHSA-8j9v-4hhh-x43c 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-8j9v-4hhh-x43c published, and has it been updated?

GHSA-8j9v-4hhh-x43c 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

Cross-Site Scripting (XSS) in TYPO3 component CSS styled contentGHSA-8j9v-4hhh-x43c

GHSA-8j9v-4hhh-x43c 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

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

Real-World Exposure

2 pkgs affected

🐘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

Failing to properly encode user input, the CSS styled content component is susceptible to Cross-Site Scripting, allowing authenticated editors to inject arbitrary HTML or JavaScript.

Affected Packages

2 total 2 fixed

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

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.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8j9v-4hhh-x43c 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 user input, the CSS styled content component is susceptible to Cross-Site Scripting, allowing authenticated editors to inject arbitrary HTML or JavaScript.

O3 Security · Impact-Aware SCA

Is GHSA-8j9v-4hhh-x43c in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works