MediumGHSA-4rpv-g4gq-rh4mCVE-2013-7073
TYPO3 vulnerable to Information Disclosure via Content Editing Wizards component
Published 17 May 2022 · Updated 8 Nov 2023
Affected packages
typo3/cmsComposer
- Affected
- >=4.5.0 <4.5.32
- Fixed in
- 4.5.32
Update to the fixed version for your release line, for example:
composer require typo3/cms:^4.5.32typo3/cmsComposer
- Affected
- >=4.7.0 <4.7.17
- Fixed in
- 4.7.17
Update to the fixed version for your release line, for example:
composer require typo3/cms:^4.7.17typo3/cmsComposer
- Affected
- >=6.0.0 <6.0.12
- Fixed in
- 6.0.12
Update to the fixed version for your release line, for example:
composer require typo3/cms:^6.0.12typo3/cmsComposer
- Affected
- >=6.1.0 <6.1.7
- Fixed in
- 6.1.7
Update to the fixed version for your release line, for example:
composer require typo3/cms:^6.1.7Details
The Content Editing Wizards component in TYPO3 4.5.0 through 4.5.31, 4.7.0 through 4.7.16, 6.0.0 through 6.0.11, and 6.1.0 through 6.1.6 does not check permissions, which allows remote authenticated editors to read arbitrary TYPO3 table columns via unspecified parameters.
Is GHSA-4rpv-g4gq-rh4m in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected typo3/cms, and gives you the command that fixes it.
References
- Advisorynvd.nist.gov/vuln/detail/CVE-2013-7073
- Packagegithub.com/TYPO3/typo3
- Linklists.opensuse.org/opensuse-security-announce/2016-08/msg00028.html
- Linklists.opensuse.org/opensuse-updates/2016-08/msg00083.html
- Linklists.opensuse.org/opensuse-updates/2016-08/msg00106.html
- Linkseclists.org/oss-sec/2013/q4/473
- Linkseclists.org/oss-sec/2013/q4/487
- Linktypo3.org/teams/security/security-bulletins/typo3-core/typo3-core-sa-2013-004
- Linkwww.debian.org/security/2014/dsa-2834
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.