GHSA-gqqf-g5r7-84vf: TYPO3 HTML Sanitizer Bypasses Cross-Site Scripting Protection
Noroxi assessment
Priority: Monitor (action score 24/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: typo3/cms-core (Packagist) 10.4.32, 11.5.16, 7.6.58.
Low priority for now. Upgrade to typo3/cms-core (Packagist) 10.4.32, 11.5.16, 7.6.58 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: OSV
> ### Meta > * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC:C` (5.7) ### Problem Due to a parsing issue in upstream package [`masterminds/html5`](https://packagist.org/packages/masterminds/html5), malicious markup used in a sequence with special HTML comments cannot be filtered and sanitized. This allows to by-pass the cross-site scripting mechanism of [`typo3/html-sanitizer`](https://github.com/TYPO3/html-sanitizer). ### Solution Update to TYPO3 version 7.6.58 ELTS, 8.7.48 ELTS, 9.5.37 ELTS, 10.4.32 or 11.5.16 that fix the problem described above. ### Credits Thanks to David Klein who reported this issue, and to TYPO3 security team member Oliver Hader who fixed the issue. ### References * [TYPO3-CORE-SA-2022-011](https://typo3.org/security/advisory/typo3-core-sa-2022-011) * [GHSA-47m6-46mj-p235](https://github.com/TYPO3/html-sanitizer/security/advisories/GHSA-47m6-46mj-p235)
- Published
- Sep 15, 2022
- Updated
- Dec 6, 2024
- EPSS
- —
- CWE
- —
Report tools
Action score
24
Low priority for now.
- CVSS
- 24 / 40 · 6.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · —
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| Packagist | typo3/cms-core | pkg:composer/typo3/cms-core |
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Packagist | typo3/cms-core | from 10.0.0 · before 10.4.32 | 10.4.32 |
| Packagist | typo3/cms-core | from 11.0.0 · before 11.5.16 | 11.5.16 |
| Packagist | typo3/cms-core | from 7.0.0 · before 7.6.58 | 7.6.58 |
| Packagist | typo3/cms-core | from 8.0.0 · before 8.7.48 | 8.7.48 |
| Packagist | typo3/cms-core | from 9.0.0 · before 9.5.37 | 9.5.37 |
Same product
Packagist: all recordsOther highest-scoring records for the same primary product.
- GHSA-cc97-g92w-jm65TYPO3 CMS Insecure Deserialization & Arbitrary Code Execution39Monitor
- GHSA-x428-565f-8xj2TYPO3 Arbitrary Code Execution and Cross-Site Scripting in Backend API35Monitor
- GHSA-f9hr-7cfq-mjg2TYPO3 Arbitrary Code Execution via File List Module35Monitor
Published before and after this one in the same product
- Later →GHSA-x4rj-f7m6-42c3May 30, 2024 · TYPO3 CMS Authentication Bypass vulnerability30Monitor
- Later →GHSA-45wj-jv2h-jwrfMay 30, 2024 · TYPO3 CMS Privilege Escalation and SQL Injection30Monitor
- Later →GHSA-wg8h-gxf4-g4ghMay 30, 2024 · TYPO3 Cross-Site Scripting in Online Media Asset Rendering24Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Packagist:typo3/cms-core | 10.4.32 | Package registry (OSV) |
| Packagist:typo3/cms-core | 11.5.16 | Package registry (OSV) |
| Packagist:typo3/cms-core | 7.6.58 | Package registry (OSV) |
| Packagist:typo3/cms-core | 8.7.48 | Package registry (OSV) |
| Packagist:typo3/cms-core | 9.5.37 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
osv
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.