GHSA-2rcw-9hrm-8q7q json
TYPO3 Cross-Site Scripting in Frontend User Login
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
Failing to properly encode user input, login status display is vulnerable to cross-site scripting in the website frontend. A valid user account is needed in order to exploit this vulnerability - either a backend user or a frontend user having the possibility to modify their user profile.
Template patterns that are affected are
- ###FEUSER_[fieldName]### using system extension felogin - <!--###USERNAME###--> for regular frontend rendering (pattern can be defined individually using TypoScript setting config.USERNAME_substToken)
Patch / fix
- packagist typo3/cms 7.6.32, 8.7.21, 9.5.2
- github.com/TYPO3/typo3@1c85fe7 commit
- github.com/TYPO3/typo3@373bec5 commit
- github.com/TYPO3/typo3@e414319 commit
Is GHSA-2rcw-9hrm-8q7q 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 | >=7.0.0, <7.6.32 >=8.0.0, <8.7.21 >=9.0.0, <9.5.2 |
7.6.32 8.7.21 9.5.2 |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
github.com
/TYPO3/typo3/commit/1c85fe70269e2ff8ecf0b6d5f16550c6cd0ddc78
web
-
github.com
/TYPO3/typo3/commit/373bec5d7d415f0764ebbadc7970610dc26da068
web
-
github.com
/TYPO3/typo3/commit/e4143195e1451630f058a58ab62d92135948a927
web
-
github.com
/FriendsOfPHP/security-advisories/blob/master/typo3/cms/2018-12-11-3.yaml
web
-
github.com
/TYPO3/typo3
package
-
typo3.org
/security/advisory/typo3-core-sa-2018-008
web
Sources
- GitHub Advisory GHSA-2rcw-9hrm-8q7q
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.