How severe is GHSA-p5j5-4j3q-8mq8?

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

Which packages are affected by GHSA-p5j5-4j3q-8mq8?

GHSA-p5j5-4j3q-8mq8 affects the following packages: typo3/html-sanitizer (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-p5j5-4j3q-8mq8?

Update typo3/html-sanitizer to 2.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p5j5-4j3q-8mq8 is resolved across your whole dependency graph.

How do I detect GHSA-p5j5-4j3q-8mq8 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/html-sanitizer. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-p5j5-4j3q-8mq8 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-p5j5-4j3q-8mq8?

O3 pinpoints whether GHSA-p5j5-4j3q-8mq8 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-p5j5-4j3q-8mq8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-p5j5-4j3q-8mq8 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 type of vulnerability is GHSA-p5j5-4j3q-8mq8?

GHSA-p5j5-4j3q-8mq8 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-p5j5-4j3q-8mq8 published, and has it been updated?

GHSA-p5j5-4j3q-8mq8 was published on June 12, 2026 and was last updated on June 12, 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

GHSA-p5j5-4j3q-8mq8

GHSA-p5j5-4j3q-8mq8 is a Cross-site Scripting (XSS) vulnerability in typo3/html-sanitizer. O3 Security confirms whether GHSA-p5j5-4j3q-8mq8 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

TYPO3 HTML Sanitizer allows Cross-site Scripting

Also known asCVE-2026-47345

Published

Jun 12, 2026

Updated

Jun 12, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🐘typo3/html-sanitizer

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

Namespace attributes are not encoded correctly during HTML serialization. This allows bypassing the cross-site scripting prevention mechanism of typo3/html-sanitizer before version 2.3.2.

Credits to Doyensec in collaboration with Claude and Anthropic Research for reporting this vulnerability.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`typo3/html-sanitizer`	all versions	2.3.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/html-sanitizer. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update typo3/html-sanitizer to 2.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p5j5-4j3q-8mq8 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 pinpoints whether GHSA-p5j5-4j3q-8mq8 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-p5j5-4j3q-8mq8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Namespace attributes are not encoded correctly during HTML serialization. This allows bypassing the cross-site scripting prevention mechanism of `typo3/html-sanitizer` before version 2.3.2. Credits to Doyensec in collaboration with Claude and Anthropic Research for reporting this vulnerability.

O3 Security · Impact-Aware SCA

Is GHSA-p5j5-4j3q-8mq8 in your dependencies?

O3 detects GHSA-p5j5-4j3q-8mq8 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works