TYPO3 CMS Allows Broken Access Control in Redirects Module
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 10.4.55, 11.5.49, 12.4.41, 13.4.23, 14.0.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Backend users with access to the redirects module and write permission on the sys_redirect table were able to read, create, and modify any redirect record without restriction to the user’s own file-mounts or web-mounts. This allowed attackers to insert or alter redirects pointing to arbitrary URLs – facilitating phishing or other malicious redirect attacks. This issue affects TYPO3 CMS versions 10.0.0-10.4.54, 11.0.0-11.5.48, 12.0.0-12.4.40, 13.0.0-13.4.22 and 14.0.0-14.0.1.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- typo3/cms-redirects
From 10.0.0 · fixed in 10.4.55; From 11.0.0 · fixed in 11.5.49; From 12.0.0 · fixed in 12.4.41; From 13.0.0 · fixed in 13.4.23; From 14.0.0 · fixed in 14.0.2
- typo3/cms-redirectsPackagist
From 14.0.0 · fixed in 14.0.2
- typo3/cms-redirectsPackagist
From 13.0.0 · fixed in 13.4.23
- typo3/cms-redirectsPackagist
From 12.0.0 · fixed in 12.4.41
- typo3/cms-redirectsPackagist
From 11.0.0 · fixed in 11.5.49
- typo3/cms-redirectsPackagist
From 10.0.0 · fixed in 10.4.55