GHSA-95qm-3xp7-vfj5: TYPO3 Cross-Site Scripting in Form Framework validation handling
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.2.1, 8.7.30, 9.5.12.
Low priority for now. Upgrade to typo3/cms-core (Packagist) 10.2.1, 8.7.30, 9.5.12 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
It has been discovered that the output of field validation errors in the Form Framework is vulnerable to cross-site scripting.
- Published
- May 30, 2024
- Updated
- Dec 6, 2024
- EPSS
- —
- CWE
- CWE-79
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.
Limit the impact of XSSCheck security headers
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 |
Limit the impact of XSS
This is a cross-site scripting (XSS) vulnerability. A well-configured Content-Security-Policy doesn't fix it, but greatly reduces its impact. Check your site's CSP and other security headers for free.
Check security headersPackage-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.2.1 | 10.2.1 |
| Packagist | typo3/cms-core | from 8.0.0 · before 8.7.30 | 8.7.30 |
| Packagist | typo3/cms-core | from 9.0.0 · before 9.5.12 | 9.5.12 |
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
- ← EarlierGHSA-82vp-jr39-4j2jMay 30, 2024 · TYPO3 Security Misconfiguration in Frontend Session Handling32Monitor
- ← EarlierGHSA-g776-759r-pf6xMay 30, 2024 · TYPO3 Broken Access Control in Import Module17Monitor
- Later →GHSA-4ppr-jw47-9qm5May 30, 2024 · TYPO3 Cross-Site Scripting in Link Handling24Monitor
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.2.1 | Package registry (OSV) |
| Packagist:typo3/cms-core | 8.7.30 | Package registry (OSV) |
| Packagist:typo3/cms-core | 9.5.12 | 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.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- GHSA-4ppr-jw47-9qm50 days apartTYPO3 Cross-Site Scripting in Link Handling24Monitor
- GHSA-6xwf-7rfm-4gwc0 days apartTYPO3 Cross-Site Scripting in Filelist Module24Monitor
- GHSA-76r3-m635-p3vc0 days apartTYPO3 Cross-Site Scripting in Language Pack Handling24Monitor
- GHSA-8c25-vj2w-p72j0 days apartTYPO3 Cross-Site Scripting in Frontend User Login24Monitor
- GHSA-g4c9-qfvw-fmr40 days apartTYPO3 Cross-Site Scripting in Backend Modal Component24Monitor
- GHSA-wg8h-gxf4-g4gh0 days apartTYPO3 Cross-Site Scripting in Online Media Asset Rendering24Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · 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)
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
osv
Root cause
User content is inserted into the page as HTML. The browser interprets the content as code rather than data.
The bug in code
The whole CWE-79 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
commentEl.innerHTML = comment.body;Fixed
commentEl.textContent = comment.body;Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
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.