Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
MEDIUM severity

GHSA-8mq9-fqv8-59wf

MEDIUM

GHSA-8mq9-fqv8-59wf is a medium-severity (CVSS 6.4) Cross-site Scripting (XSS) vulnerability in typo3/cms-core. O3 Security confirms whether GHSA-8mq9-fqv8-59wf is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Cross-Site Scripting in Page Preview

Also known asBIT-typo3-2021-32667CVE-2021-32667
Published
Jul 22, 2021
Updated
Jul 8, 2026
Affected
6 pkgs
Patched
6 / 6
Exploits
None indexed
Exploitation data as of Jul 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

6 pkgs affected
🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms🐘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

Meta

  • CVSS: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC (5.0)

Problem

Failing to properly encode Page TSconfig settings, corresponding page preview module (Web>View) is vulnerable to persistent cross-site scripting. A valid backend user account is needed to exploit this vulnerability.

Solution

Update to TYPO3 versions 9.5.28, 10.4.18, 11.3.1 that fix the problem described.

Credits

Thanks to TYPO3 core merger Oliver Bartsch who reported and fixed the issue.

References

Affected Packages

6 total 6 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagisttypo3/cms-core9.0.0&&< 9.5.289.5.28
🐘Packagisttypo3/cms-core10.0.0&&< 10.4.1810.4.18
🐘Packagisttypo3/cms-core11.0.0&&< 11.3.111.3.1
🐘Packagisttypo3/cms10.0.0&&< 10.4.1810.4.18
🐘Packagisttypo3/cms11.0.0&&< 11.3.111.3.1
🐘Packagisttypo3/cms9.0.0&&< 9.5.289.5.28

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-core. 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.

  2. Fix

    Update typo3/cms-core to 9.5.28 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8mq9-fqv8-59wf is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-8mq9-fqv8-59wf 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-8mq9-fqv8-59wf. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

> ### Meta > * CVSS: `CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC` (5.0) ### Problem Failing to properly encode _Page TSconfig_ settings, corresponding page preview module (_Web>View_) is vulnerable to persistent cross-site scripting. A valid backend user account is needed to exploit this vulnerability. ### Solution Update to TYPO3 versions 9.5.28, 10.4.18, 11.3.1 that fix the problem described. ### Credits Thanks to TYPO3 core merger Oliver Bartsch who reported and fixed the issue. ### References * [TYPO3-CORE-SA-2021-009](https://typo3.org/security/advisory/typo3-core-sa-202
O3 Security · Impact-Aware SCA

Is GHSA-8mq9-fqv8-59wf in your dependencies?

O3 detects GHSA-8mq9-fqv8-59wf across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-8mq9-fqv8-59wf: Cross-Site Scripting… | O3 Security