CVE-2012-6146: XSS
Published May 20, 2014
·Updated
The Backend History Module in TYPO3 4.5.x before 4.5.21, 4.6.x before 4.6.14, and 4.7.x before 4.7.6 does not properly restrict access, which allows remote authenticated editors to read the history of arbitrary records via a crafted URL.
Affected Software
46 affected componentsFixes available
composer/typo3/cms>=4.7<4.7.6
4.7.6
composer/typo3/cms>=4.6<4.6.14
4.6.14
composer/typo3/cms>=4.5<4.5.21
4.5.21
Typo3 TYPO3=4.6.0
Typo3 TYPO3=4.6.1
Typo3 TYPO3=4.6.2
Typo3 TYPO3=4.6.3
Typo3 TYPO3=4.6.4
Typo3 TYPO3=4.6.5
Typo3 TYPO3=4.6.6
Typo3 TYPO3=4.6.7
Typo3 TYPO3=4.6.8
Typo3 TYPO3=4.6.9
Typo3 TYPO3=4.6.10
Typo3 TYPO3=4.6.11
Typo3 TYPO3=4.6.12
Typo3 TYPO3=4.6.13
Typo3 TYPO3=4.7
Typo3 TYPO3=4.7.0
Typo3 TYPO3=4.7.1
Typo3 TYPO3=4.7.2
Typo3 TYPO3=4.7.3
Typo3 TYPO3=4.7.4
Typo3 TYPO3=4.7.5
Typo3 TYPO3=4.5
Typo3 TYPO3=4.5.0
Typo3 TYPO3=4.5.1
Typo3 TYPO3=4.5.2
Typo3 TYPO3=4.5.3
Typo3 TYPO3=4.5.4
Typo3 TYPO3=4.5.5
Typo3 TYPO3=4.5.6
Typo3 TYPO3=4.5.7
Typo3 TYPO3=4.5.8
Typo3 TYPO3=4.5.9
Typo3 TYPO3=4.5.10
Typo3 TYPO3=4.5.11
Typo3 TYPO3=4.5.12
Typo3 TYPO3=4.5.13
Typo3 TYPO3=4.5.14
Typo3 TYPO3=4.5.15
Typo3 TYPO3=4.5.16
Typo3 TYPO3=4.5.17
Typo3 TYPO3=4.5.18
Typo3 TYPO3=4.5.19
Typo3 TYPO3=4.5.20
Event History
May 20, 2014
CVE Published
via MITRE·02:00 PM
Data Sourced
via MITRE·02:00 PM
Description
Data Sourced
via NVD·02:55 PM
DescriptionSeverityWeaknessAffected Software
May 17, 2022
Advisory Published
via GitHub·04:43 AM
Frequently Asked Questions
1
What is the severity of CVE-2012-6146?
CVE-2012-6146 has a low to medium severity level due to improper access restrictions.
2
How do I fix CVE-2012-6146?
To fix CVE-2012-6146, upgrade your TYPO3 installation to at least version 4.5.21, 4.6.14, or 4.7.6.
3
What versions of TYPO3 are affected by CVE-2012-6146?
CVE-2012-6146 affects TYPO3 versions prior to 4.5.21, 4.6.14, and 4.7.6.
4
Can remote authenticated users exploit CVE-2012-6146?
Yes, remote authenticated users can exploit CVE-2012-6146 to access the history of arbitrary records through crafted URLs.
5
Is there a workaround for CVE-2012-6146?
There is no official workaround for CVE-2012-6146; the recommended action is to update to a secure version.