How severe is GHSA-cg75-qfg2-w9hj?

No CVSS score has been assigned to GHSA-cg75-qfg2-w9hj yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-cg75-qfg2-w9hj?

GHSA-cg75-qfg2-w9hj affects the following packages: typo3/cms-core (Packagist), typo3/cms-core (Packagist), typo3/cms-indexed-search (Packagist), typo3/cms-indexed-search (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-cg75-qfg2-w9hj?

Update typo3/cms-core to 13.4.31 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cg75-qfg2-w9hj is resolved across your whole dependency graph.

How do I detect GHSA-cg75-qfg2-w9hj in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-cg75-qfg2-w9hj 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-cg75-qfg2-w9hj actively exploited in the wild?

No public exploit code has been indexed for GHSA-cg75-qfg2-w9hj 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.

What is the EPSS score for GHSA-cg75-qfg2-w9hj?

GHSA-cg75-qfg2-w9hj has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 40th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-cg75-qfg2-w9hj?

GHSA-cg75-qfg2-w9hj is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-cg75-qfg2-w9hj published, and has it been updated?

GHSA-cg75-qfg2-w9hj was published on June 12, 2026 and was last updated on September 10, 2026. 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 CMS has Cross-Site Scripting in Indexed SearchGHSA-cg75-qfg2-w9hj

Fix: TYPO3/typo3@2e96dd0

GHSA-cg75-qfg2-w9hj is a Cross-site Scripting (XSS) vulnerability in typo3/cms-core. A fix is available for typo3/cms-core — see the affected versions and patch details below.

Also known asCVE-2026-47348

Published

Jun 12, 2026

Updated

Sep 10, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-cg75-qfg2-w9hj.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs40th percentile — riskier than 40% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

4 pkgs affected

🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-indexed-search🐘typo3/cms-indexed-search

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

Problem

Editors with access to create or modify page content were able to include HTML markup in page titles that were stored in the search index without sanitization. When displayed in frontend search results via the Indexed Search plugin, these titles were rendered without proper output encoding, resulting in a Cross-Site Scripting vulnerability.

Solution

Update to TYPO3 versions 13.4.31 LTS, 14.3.3 LTS that fix the problem described.

Credits

TYPO3 CMS thanks Jan Kahmen and Sanjay Singh Jhala for reporting this issue, and to TYPO3 core & security team member Oliver Hader for fixing it.

Resources

TYPO3-CORE-SA-2026-010

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`typo3/cms-core`	≥ 13.0.0&&< 13.4.31	13.4.31`composer require typo3/cms-core:^13.4.31`
🐘Packagist	`typo3/cms-core`	≥ 14.0.0&&< 14.3.3	14.3.3`composer require typo3/cms-core:^14.3.3`
🐘Packagist	`typo3/cms-indexed-search`	≥ 13.0.0&&< 13.4.31	13.4.31`composer require typo3/cms-indexed-search:^13.4.31`
🐘Packagist	`typo3/cms-indexed-search`	≥ 14.0.0&&< 14.3.3	14.3.3`composer require typo3/cms-indexed-search:^14.3.3`

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-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update typo3/cms-core to 13.4.31 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cg75-qfg2-w9hj 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

### Problem Editors with access to create or modify page content were able to include HTML markup in page titles that were stored in the search index without sanitization. When displayed in frontend search results via the Indexed Search plugin, these titles were rendered without proper output encoding, resulting in a Cross-Site Scripting vulnerability. ### Solution Update to TYPO3 versions 13.4.31 LTS, 14.3.3 LTS that fix the problem described. ### Credits TYPO3 CMS thanks Jan Kahmen and Sanjay Singh Jhala for reporting this issue, and to TYPO3 core & security team member Oliver Hader for fi

O3 Security · Impact-Aware SCA

Is GHSA-cg75-qfg2-w9hj in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works