Skip to content
Fencer Intel
medium 6.3

CVE-2013-7075 json

TYPO3 vulnerable to Insecure Unserialize via Content Editing Wizards component

published 12y ago modified 4mo ago also GHSA-47ww-mq32-g4xw , EUVD-2022-2335

cvss
6.3
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
1.3%
EPSS 1.3% chance of exploitation in 30 days, percentile 70%
public exploits
0
none known

Summary

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 allows remote authenticated backend users to unserialize arbitrary PHP objects, delete arbitrary files, and possibly have other unspecified impacts via an unspecified parameter, related to a "missing signature."

Patch / fix

  • packagist typo3/cms 4.5.32, 4.7.17, 6.0.12, 6.1.7

Is CVE-2013-7075 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 Fencer

Exploit prediction

1.27% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 6.5 AV:N/AC:L/Au:S/C:P/I:P/A:P
GitHub 3.1 6.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Affected packages

ecosystem package affected fixed in
packagist typo3/cms
>=4.5.0, <4.5.32
>=4.7.0, <4.7.17
>=6.0.0, <6.0.12
>=6.1.0, <6.1.7
4.5.32
4.7.17
6.0.12
6.1.7

Classification

Weakness
  • CWE-310 Cryptographic Issues
  • CWE-502 Deserialization of Untrusted Data

References

Sources

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.