
20/5/2014

17/5/2022

6/8/2024
CVE-2012-6146: XSS
First published: Tue 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.
Credit: secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|
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 | =4.6.0 | |
TYPO3 | =4.6.1 | |
TYPO3 | =4.6.2 | |
TYPO3 | =4.6.3 | |
TYPO3 | =4.6.4 | |
TYPO3 | =4.6.5 | |
TYPO3 | =4.6.6 | |
TYPO3 | =4.6.7 | |
TYPO3 | =4.6.8 | |
TYPO3 | =4.6.9 | |
TYPO3 | =4.6.10 | |
TYPO3 | =4.6.11 | |
TYPO3 | =4.6.12 | |
TYPO3 | =4.6.13 | |
TYPO3 | =4.7 | |
TYPO3 | =4.7.0 | |
TYPO3 | =4.7.1 | |
TYPO3 | =4.7.2 | |
TYPO3 | =4.7.3 | |
TYPO3 | =4.7.4 | |
TYPO3 | =4.7.5 | |
TYPO3 | =4.5 | |
TYPO3 | =4.5.0 | |
TYPO3 | =4.5.1 | |
TYPO3 | =4.5.2 | |
TYPO3 | =4.5.3 | |
TYPO3 | =4.5.4 | |
TYPO3 | =4.5.5 | |
TYPO3 | =4.5.6 | |
TYPO3 | =4.5.7 | |
TYPO3 | =4.5.8 | |
TYPO3 | =4.5.9 | |
TYPO3 | =4.5.10 | |
TYPO3 | =4.5.11 | |
TYPO3 | =4.5.12 | |
TYPO3 | =4.5.13 | |
TYPO3 | =4.5.14 | |
TYPO3 | =4.5.15 | |
TYPO3 | =4.5.16 | |
TYPO3 | =4.5.17 | |
TYPO3 | =4.5.18 | |
TYPO3 | =4.5.19 | |
TYPO3 | =4.5.20 | |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the severity of CVE-2012-6146?
CVE-2012-6146 has a low to medium severity level due to improper access restrictions.
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.
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.
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.
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.
- agent/type
- agent/references
- agent/severity
- agent/author
- agent/weakness
- agent/description
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-2hp4-8h6h-93rr
- alias/CVE-2012-6146
- agent/software-canonical-lookup
- collector/github-advisory
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/trending
- agent/source
- agent/tags
- agent/softwarecombine
- collector/nvd-cve
- source/NVD
- agent/software-canonical-lookup-request
- collector/nvd-index
- package-manager/composer
- vendor/typo3
- canonical/typo3 typo3
- version/typo3 typo3/4.6.0
- version/typo3 typo3/4.6.1
- version/typo3 typo3/4.6.2
- version/typo3 typo3/4.6.3
- version/typo3 typo3/4.6.4
- version/typo3 typo3/4.6.5
- version/typo3 typo3/4.6.6
- version/typo3 typo3/4.6.7
- version/typo3 typo3/4.6.8
- version/typo3 typo3/4.6.9
- version/typo3 typo3/4.6.10
- version/typo3 typo3/4.6.11
- version/typo3 typo3/4.6.12
- version/typo3 typo3/4.6.13
- version/typo3 typo3/4.7
- version/typo3 typo3/4.7.0
- version/typo3 typo3/4.7.1
- version/typo3 typo3/4.7.2
- version/typo3 typo3/4.7.3
- version/typo3 typo3/4.7.4
- version/typo3 typo3/4.7.5
- version/typo3 typo3/4.5
- version/typo3 typo3/4.5.0
- version/typo3 typo3/4.5.1
- version/typo3 typo3/4.5.2
- version/typo3 typo3/4.5.3
- version/typo3 typo3/4.5.4
- version/typo3 typo3/4.5.5
- version/typo3 typo3/4.5.6
- version/typo3 typo3/4.5.7
- version/typo3 typo3/4.5.8
- version/typo3 typo3/4.5.9
- version/typo3 typo3/4.5.10
- version/typo3 typo3/4.5.11
- version/typo3 typo3/4.5.12
- version/typo3 typo3/4.5.13
- version/typo3 typo3/4.5.14
- version/typo3 typo3/4.5.15
- version/typo3 typo3/4.5.16
- version/typo3 typo3/4.5.17
- version/typo3 typo3/4.5.18
- version/typo3 typo3/4.5.19
- version/typo3 typo3/4.5.20
Contact
SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.coBy using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203