Cross-Site Scripting in TYPO3 Backend

published 2024-06-05 2y ago modified 2024-12-02 last yr.

cvss: 4.6; version 3.1, GitHub
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

Failing to properly encode user input, some backend components are vulnerable to Cross-Site Scripting. A valid backend user account is needed to exploit this vulnerability.

Patch / fix

fixed in 1

packagist typo3/cms 6.2.20, 7.6.5, 8.0.1

Is GHSA-5wx6-xwxf-q8qj 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

CVSS scores

assigned by	version	score	vector
GitHub	3.1	4.6	CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N

Affected packages

ecosystem	package	affected	fixed in
packagist	typo3/cms	>=6.2.0, <6.2.20 >=7.6.0, <7.6.5 >=8.0.0, <8.0.1	6.2.20 7.6.5 8.0.1

Classification

Weakness

CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

GitHub Advisory GHSA-5wx6-xwxf-q8qj

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.