GHSA-wp8j-c736-c5r3 json
TYPO3 Cross-Site Scripting Vulnerability Exploitable by Editors
published 2y ago modified last yr.
- cvss
- 5.4
- 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
Summary
It has been discovered that link tags generated by typolink functionality in the website's frontend are vulnerable to cross-site scripting - values being assigned to HTML attributes have not been parsed correctly. A valid backend user account is needed to exploit this vulnerability.
As second and separate vulnerability in the filelist module of the backend user interface has been referenced with this advisory as well. Error messages being shown after using a malicious name for renaming a file are not propery encoded, thus vulnerable to cross-site scripting. A valid backend user account is needed to exploit this vulnerability.
Patch / fix
- packagist typo3/cms 6.2.14, 7.3.1
- github.com/TYPO3/typo3@7695d91 commit
- github.com/TYPO3/typo3@d7feb40 commit
Is GHSA-wp8j-c736-c5r3 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 FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | typo3/cms | >=6.2.0, <6.2.14 >=7.0.0, <7.3.1 |
6.2.14 7.3.1 |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
github.com
/TYPO3/typo3/commit/7695d91fca1a96a3a3e7466097ae92c32b1130d8
web
-
github.com
/TYPO3/typo3/commit/d7feb40c8d277c6b6ab3a548313be1e1a2084299
web
-
github.com
/FriendsOfPHP/security-advisories/blob/master/typo3/cms/2015-07-01-3.yaml
web
-
github.com
/TYPO3/typo3
package
-
typo3.org
/security/advisory/typo3-core-sa-2015-004
web
-
typo3.org
/teams/security/security-bulletins/typo3-core/typo3-core-sa-2015-004
web
Sources
- GitHub Advisory GHSA-wp8j-c736-c5r3
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.