CVE-2020-26227: Cross-Site Scripting in Fluid view helpers
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.
- Probability of exploitation in the next 30 days: 0.72% (FIRST EPSS); higher than 54.5% of all records.
- 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 (Packagist) 10.4.10, 8.7.38, 9.5.23; typo3/cms-core (Packagist) 10.4.10, 8.7.38, 9.5.23.
Low priority for now. Upgrade to typo3/cms (Packagist) 10.4.10, 8.7.38, 9.5.23; typo3/cms-core (Packagist) 10.4.10, 8.7.38, 9.5.23 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: NVD · CVE.org · FIRST EPSS
TYPO3 is an open source PHP based web content management system. In TYPO3 before versions 9.5.23 and 10.4.10 the system extension Fluid (typo3/cms-fluid) of the TYPO3 core is vulnerable to cross-site scripting passing user-controlled data as argument to Fluid view helpers. Update to TYPO3 versions 9.5.23 or 10.4.10 that fix the problem described.
- Published
- Nov 23, 2020
- Updated
- Jun 16, 2026
- EPSS
- 0.7% · 54th percentile
- 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 · 0.7%
CNA vs NVD score
- NVD
- 6.1
- CNA · GitHub_M
- 6.1
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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 |
|---|---|---|
| typo3 | typo3 | cpe:2.3:a:typo3:typo3 |
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 headersVersions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
TYPO3 TYPO3.CMS
- >= 9.0.0, < 9.5.23, >= 10.0.0, < 10.4.10affected
Affected versions · NVD (5)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- typo3 typo36.2.0 and later · before 6.2.54
- typo3 typo37.6.0 and later · before 7.6.48
- typo3 typo38.7.0 and later · before 8.7.38
- typo3 typo39.0.0 and later · before 9.5.23
- typo3 typo310.0.0 and later · before 10.4.10
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 | from 10.0.0 · before 10.4.10 | 10.4.10 |
| Packagist | typo3/cms | from 8.7.0 · before 8.7.38 | 8.7.38 |
| Packagist | typo3/cms | from 9.0.0 · before 9.5.23 | 9.5.23 |
| Packagist | typo3/cms-core | from 10.0.0 · before 10.4.10 | 10.4.10 |
| Packagist | typo3/cms-core | from 8.7.0 · before 8.7.38 | 8.7.38 |
| Packagist | typo3/cms-core | from 9.0.0 · before 9.5.23 | 9.5.23 |
Same product
typo3: all recordsOther highest-scoring records for the same primary product.
- CVE-2009-0255The System extension Install tool in TYPO3 4.0.0 through 4.0.9, 4.1.0 through 4.1.7, and 4.2.0 through 4.2.3 creates the encryption key…60This week
- CVE-2013-6288Unspecified vulnerability in the Apache Solr for TYPO3 (solr) extension before 2.8.3 for TYPO3 has unknown impact and remote attack…41Plan
- CVE-2013-5303Unspecified vulnerability in the Store Locator (locator) extension before 3.1.5 for TYPO3 has unknown impact and remote attack vectors…41Plan
Published before and after this one in the same product
- ← EarlierCVE-2020-15098Jul 29, 2020 · Missing Required Cryptographic Step Leading to Sensitive Information Disclosure in TYPO3 CMS36Monitor
- ← EarlierCVE-2020-15099Jul 29, 2020 · Exposure of Sensitive Information to an Unauthorized Actor in TYPO3 CMS33Monitor
- Later →CVE-2020-26228Nov 23, 2020 · Cleartext storage of session identifier30Monitor
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 | 10.4.10 | Package registry (OSV) |
| Packagist:typo3/cms | 8.7.38 | Package registry (OSV) |
| Packagist:typo3/cms | 9.5.23 | Package registry (OSV) |
| Packagist:typo3/cms-core | 10.4.10 | Package registry (OSV) |
| Packagist:typo3/cms-core | 8.7.38 | Package registry (OSV) |
| Packagist:typo3/cms-core | 9.5.23 | 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.
Not on record for this CVE: EPSS history · patch commit or PR link · 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)
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
nvd-primary
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. →