TYPO3CMS
CVE-2021-32667
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedTYPO3 is an open source PHP based web content management system. Versions 9.0.0 through 9.5.28, 10.0.0 through 10.4.17, and 11.0.0 through 11.3.0 have a cross-site scripting vulnerability. When _Page TSconfig_ settings are not properly encoded, corresponding page preview module (_Web>View_) is vulnerable to persistent cross-site scripting. A valid backend user account is needed to exploit this vulnerability. TYPO3 versions 9.5.29, 10.4.18, 11.3.1 contain a patch for this issue.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceStored XSS vulnerability in TYPO3 where Page TSconfig settings are not properly encoded before being rendered in the page preview module (Web>View). An authenticated backend user can inject malicious scripts that persist and execute when other users view the affected page.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
TYPO3CMS
>= 9.0.0, <= 9.5.287>= 10.0.0, <= 10.4.17>= 11.0.0, <= 11.3.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed TYPO3 versionLog into the TYPO3 backend and navigate to Admin Tools > About or check the composer.json file for the 'typo3/cms' version entryAffected if The installed version falls within >= 9.0.0 to 9.5.287, >= 10.0.0 to 10.4.17, or >= 11.0.0 to 11.3.0
-
Verify backend access existsConfirm that backend user accounts exist with permissions to modify Page TSconfig (typically admin or page editors)Affected if Any authenticated backend user with Page TSconfig editing rights exists in the system
-
Inspect Page TSconfig entriesIn the backend, go to Web > Page and select a page. Click 'Resources' and view the Page TSconfig field. Alternatively, query the database table 'pages' for non-empty 'tsconfig' field valuesAffected if Any Page TSconfig contains unsanitized HTML or script tags (look for <script>, javascript:, onload, onerror attributes)
-
Review page preview outputNavigate to Web > View and preview a page that has custom Page TSconfig defined. Inspect the HTML source of the preview to see if TSconfig values are rendered unencodedAffected if Page TSconfig values appear as raw text in the preview HTML without HTML entity encoding (e.g., < appears as < instead of <)
A user is affected if they run a TYPO3 version within the affected ranges AND have backend users with access to modify Page TSconfig, with malicious entries already present in the system.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade TYPO3 to version 9.5.29, 10.4.18, 11.3.1 or later to apply the patch that properly encodes Page TSconfig output.
Fix this in TYPO3
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-32667 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-32667 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data