How severe is GHSA-hww5-6x85-mc24?

No CVSS score has been assigned to GHSA-hww5-6x85-mc24 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-hww5-6x85-mc24?

GHSA-hww5-6x85-mc24 affects the following packages: typo3/cms (Packagist), typo3/cms (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-hww5-6x85-mc24?

Update typo3/cms to 8.7.27 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hww5-6x85-mc24 is resolved across your whole dependency graph.

How do I detect GHSA-hww5-6x85-mc24 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-hww5-6x85-mc24 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-hww5-6x85-mc24 actively exploited in the wild?

No public exploit code has been indexed for GHSA-hww5-6x85-mc24 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-hww5-6x85-mc24 published, and has it been updated?

GHSA-hww5-6x85-mc24 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.

Typo3 Arbitrary Code Execution and Cross-Site Scripting…

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

Backend API configuration using Page TSconfig is vulnerable to arbitrary code execution and cross-site scripting. TSconfig fields of page properties in backend forms can be used to inject malicious sequences. Field tsconfig_includes is vulnerable to directory traversal leading to same scenarios as having direct access to TSconfig settings.

A valid backend user account having access to modify values for fields pages.TSconfig and pages.tsconfig_includes is needed in order to exploit this vulnerability.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`typo3/cms`	≥ 8.0.0&&< 8.7.27	8.7.27`composer require typo3/cms:^8.7.27`
🐘Packagist	`typo3/cms`	≥ 9.0.0&&< 9.5.8	9.5.8`composer require typo3/cms:^9.5.8`

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 8.7.27 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hww5-6x85-mc24 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

Backend API configuration using Page TSconfig is vulnerable to arbitrary code execution and cross-site scripting. TSconfig fields of page properties in backend forms can be used to inject malicious sequences. Field tsconfig_includes is vulnerable to directory traversal leading to same scenarios as having direct access to TSconfig settings. A valid backend user account having access to modify values for fields pages.TSconfig and pages.tsconfig_includes is needed in order to exploit this vulnerability.

O3 Security · Impact-Aware SCA

Is GHSA-hww5-6x85-mc24 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

Typo3 Arbitrary Code Execution and Cross-Site Scripting in Backend APIGHSA-hww5-6x85-mc24