LiveActive security incident?Get immediate response
CVE Record

CVE-2021-32669: Cross-Site Scripting in Backend Grid View

TYPO3 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 settings for _backend layouts_ are not properly encoded, the corresponding grid 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 vulnerability.

MediumCVSS 6.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

TYPO3 CMS had a persistent cross-site scripting flaw in the backend grid view. An attacker needs a valid backend account, so this is mainly an insider or compromised-account risk. Successful abuse could affect confidentiality and integrity for administrators or editors using vulnerable backend layouts.

Executive priority

Prioritize normal patch management unless backend accounts are shared, weakly protected, or exposed to many editors. Escalate if affected TYPO3 instances support sensitive content or privileged administrative workflows.

Technical view

CVE-2021-32669 is CWE-79 in TYPO3.CMS backend layout setting encoding. Affected versions are 9.0.0-9.5.28, 10.0.0-10.4.17, and 11.0.0-11.3.0. The issue is persistent XSS in the backend grid view, with network reachability, low privileges, high complexity, and required user interaction.

Likely exposure

Exposure is limited to TYPO3 CMS deployments running the affected branches where backend users can access or influence backend layout settings shown in grid view. Public anonymous exploitation is not indicated by the supplied sources.

Exploitation context

The sources state a valid backend user account is required. The bundle does not show CISA KEV listing or cited evidence of active exploitation. Treat this as a credible authenticated CMS risk, especially where backend accounts are broadly assigned.

Researcher notes

Focus validation on TYPO3 core version and backend layout/grid view usage. The provided sources name patched versions but do not provide indicators of compromise or active exploit evidence. Avoid assuming other TYPO3 extensions are affected.

Mitigation direction

  • Upgrade TYPO3 CMS to 9.5.29, 10.4.18, 11.3.1, or later supported versions.
  • Review TYPO3 vendor advisory for branch-specific patch guidance.
  • Restrict backend accounts to trusted users with least privilege.
  • Remove stale backend users and enforce strong account protection.

Validation and detection

  • Inventory TYPO3 CMS versions across production, staging, and managed hosting.
  • Confirm no deployment runs 9.5.28, 10.4.17, 11.3.0, or earlier affected versions.
  • Review who can manage backend layout settings.
  • Verify vulnerability scanner or asset records reflect the patched TYPO3 version.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-32669 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:N1.25.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.4Medium
CVSS 3.1 vector shape for CVE-2021-32669Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
TYPO3TYPO3.CMS>= 9.0.0, < 9.5.29, >= 10.0.0, < 10.4.18, >= 11.0.0, < 11.3.1Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.