CVE-2014-3946 json
Typo3 Information Disclosure
published 12y ago modified 4mo ago also GHSA-vccp-5v5h-p8m6 , EUVD-2022-5337
- cvss
- 4.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 66%
- public exploits
- 0
- none known
Summary
The query caching functionality in the Extbase Framework component in TYPO3 6.2.0 before 6.2.3 does not properly validate group permissions, which allows remote authenticated users to read arbitrary queries via unspecified vectors.
Patch / fix
- packagist typo3/cms 6.2.3
Is CVE-2014-3946 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 FencerExploit prediction
1.12% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | typo3/cms | >=6.2.0, <6.2.3 |
6.2.3 |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
debian.org
/security/2014/dsa-2942
vendor-advisory, web
-
typo3.org
/teams/security/security-bulletins/typo3-core/typo3-core-sa-2014-001/
vendor-advisory
-
openwall.com
/lists/oss-security/2014/06/03/2
mailing-list, web
-
nvd.nist.gov
/vuln/detail/CVE-2014-3946
advisory
-
github.com
/FriendsOfPHP/security-advisories/blob/master/typo3/cms/CVE-2014-3946.yaml
web
-
github.com
/TYPO3/typo3
package
-
typo3.org
/security/advisory/typo3-core-sa-2014-001
web
-
typo3.org
/teams/security/security-bulletins/typo3-core/typo3-core-sa-2014-001
web
Sources
- CVE List CVE-2014-3946
- GitHub Advisory GHSA-vccp-5v5h-p8m6
- NVD CVE-2014-3946
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.