CVE-2012-3527 json
TYPO3 allows remote authenticated backend users to unserialize arbitrary objects
published 2012-09-05 14 y ago modified 2026-06-16 4 mo ago also GHSA-m4hw-r893-xh4g , EUVD-2012-3482
- cvss
- 4.6
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.1%
- EPSS 2.1% chance of exploitation in 30 days, percentile 82%
- public exploits
- 0
- none known
Summary
view_help.php in the backend help system in TYPO3 4.5.x before 4.5.19, 4.6.x before 4.6.12 and 4.7.x before 4.7.4 allows remote authenticated backend users to unserialize arbitrary objects and possibly execute arbitrary PHP code via an unspecified parameter, related to a "missing signature (HMAC)."
Patch / fix
- packagist typo3/cms 4.5.19, 4.6.12, 4.7.4
- typo3 typo3 4.5.19, 4.6.12, 4.7.4
Exploit prediction
2.12% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.6 | AV:N/AC:H/Au:S/C:P/I:P/A:P |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | typo3/cms | >=4.5.0, <4.5.19 >=4.6.0, <4.6.12 >=4.7.0, <4.7.4 |
4.5.19 4.6.12 4.7.4 |
Classification
- Weakness
-
- CWE-502 Deserialization of Untrusted Data
References
-
debian.org
/security/2012/dsa-2537
vendor-advisory, web, third-party-advisory
-
typo3.org
/teams/security/security-bulletins/typo3-core/typo3-core-sa-2012-004/
vendor-advisory
-
openwall.com
/lists/oss-security/2012/08/22/8
mailing-list, web
-
exchange.xforce.ibmcloud.com
/vulnerabilities/77791
vdb-entry, web, third-party-advisory
-
osvdb.org
/84773
vdb-entry, broken-link
-
secunia.com
/advisories/50287
third-party-advisory, not-applicable
-
nvd.nist.gov
/vuln/detail/CVE-2012-3527
advisory
-
github.com
/TYPO3/typo3
package
-
web.archive.org
/web/20120817233148/http://typo3.org/teams/security/security-bulletins/typo3-core/typo3-core-sa-2012-004
web
Sources
- CVE List CVE-2012-3527
- GitHub Advisory GHSA-m4hw-r893-xh4g
- NVD CVE-2012-3527
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.