LiveActive security incident?Get immediate response
CVE Record

CVE-2020-26229: XML External Entity in Dashboard Widget

TYPO3 is an open source PHP based web content management system. In TYPO3 from version 10.4.0, and before version 10.4.10, RSS widgets are susceptible to XML external entity processing. This vulnerability is reasonable, but is theoretical - it was not possible to actually reproduce the vulnerability with current PHP versions of supported and maintained system distributions. At least with libxml2 version 2.9, the processing of XML external entities is disabled per default - and cannot be exploited. Besides that, a valid backend user account is needed. Update to TYPO3 version 10.4.10 to fix the problem described.

LowCVSS 3.7Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

TYPO3 CMS RSS dashboard widgets could process XML external entities, a bug class that may expose limited data or affect availability. The vendor rates this low because exploitation needs a valid backend user and interaction, and was described as theoretical on supported PHP/libxml2 stacks. Upgrade to TYPO3 10.4.10.

Executive priority

Treat as routine maintenance unless an affected TYPO3 backend is broadly accessible or poorly controlled. The business risk is limited by required backend access, user interaction, high complexity, and vendor-reported non-reproducibility on supported stacks. Still patch to remove avoidable exposure.

Technical view

CWE-611 in TYPO3 backend RSS widgets. CVSS 3.1 score is 3.7 with high attack complexity, low privileges, and user interaction required. Sources say libxml2 2.9 disables external entity processing by default, and the vendor could not reproduce exploitation on current supported distributions.

Likely exposure

Primary exposure is TYPO3 CMS 10.x installations before 10.4.10, especially where backend users can configure or interact with RSS dashboard widgets. The bundle conflicts slightly on lower affected bounds, so inventory all TYPO3 10.x systems and prioritize versions below 10.4.10.

Exploitation context

The provided sources do not report active exploitation, and this CVE is not listed as KEV. Vendor text describes the issue as theoretical, requiring a valid backend account and conditions where XML external entity processing is possible despite modern libxml2 defaults.

Researcher notes

Evidence supports low severity and theoretical exploitability only. Do not assume exploitability on modern distributions without environment validation. The source bundle includes inconsistent affected-version wording: description names 10.4.0 to before 10.4.10, while affected metadata says 10.0.0 to before 10.4.10.

Mitigation direction

  • Upgrade TYPO3 CMS to version 10.4.10 or later.
  • Restrict TYPO3 backend access to trusted users only.
  • Review vendor advisory for environment-specific guidance.
  • Confirm maintained PHP and libxml2 versions are in use.

Validation and detection

  • Inventory TYPO3 CMS versions across production and staging.
  • Identify systems running TYPO3 10.x below 10.4.10.
  • Check whether RSS dashboard widgets are enabled or used.
  • Confirm backend access controls limit low-privileged users.
  • Document PHP and libxml2 versions for affected hosts.
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 · low confidence lookup

CWE-611: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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-2020-26229 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
Low
CVSS
3.7 (3.1)
Known Exploited
No
Published

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

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
3.7CVSS 3.1LowCVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:L1.22.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

3.7Low
CVSS 3.1 vector shape for CVE-2020-26229Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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>= 10.0.0, < 10.4.10Listed
Weakness

CWE details

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

CWE-611 · source CWE mapping

Improper Restriction of XML External Entity Reference

Improper Restriction of XML External Entity Reference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.