Skip to content
Fencer Vulns
low 3.7

CVE-2020-26229 json

XML External Entity in Dashboard Widget

published 2020-11-23 5 y ago modified 2026-07-08 4 mo ago also BIT-typo3-2020-26229 , EUVD-2020-1468 , GHSA-q9cp-mc96-m4w2

cvss
3.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 51%
public exploits
0
none known

Summary

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.

Patch / fix

  • packagist typo3/cms-core 10.4.10
  • packagist typo3/cms 10.4.10
  • bitnami typo3 10.4.10
  • typo3 typo3 10.4.10

Exploit prediction

0.64% chance of exploitation in the next 30 days, higher than 51% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 3.7 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:L
GitHub 3.1 3.7 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:L
NVD 3.1 3.7 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:L
NVD 2.0 3.6 AV:N/AC:H/Au:S/C:P/I:N/A:P
OSV 3.1 3.7 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:L

Affected packages

ecosystem package affected fixed in
packagist typo3/cms-core
>=10.0.0, <10.4.10
10.4.10
packagist typo3/cms
>=10.0.0, <10.4.10
10.4.10
bitnami typo3
>=10.0.0, <10.4.10
10.4.10

Affected products

  • TYPO3 TYPO3.CMS

Classification

Weakness
  • CWE-611 Improper Restriction of XML External Entity Reference

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.