Skip to content
Fencer Intel
high —

GHSA-qffc-gwpp-m2xr json

XML External Entity (XXE) Processing in TYPO3 Core

published 2y ago modified last yr.

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

All XML processing within the TYPO3 CMS are vulnerable to XEE processing. This can lead to load internal and/or external (file) content within an XML structure. Furthermore it is possible to inject arbitrary files for an XML Denial of Service attack. For more information on that topic see https://www.owasp.org/index.php/XML_External_Entity_(XXE)_Processing.

Patch / fix

  • packagist typo3/cms 6.2.19, 7.6.4

Is GHSA-qffc-gwpp-m2xr in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
packagist typo3/cms
>=6.2.0, <6.2.19
>=7.6.0, <7.6.4
6.2.19
7.6.4

References

Sources

Fencer Intel 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.