Skip to content
Fencer Vulns
high 8.8

CVE-2020-15098 json

Missing Required Cryptographic Step Leading to Sensitive Information Disclosure in TYPO3 CMS

published 2020-07-29 6 y ago modified 2026-07-08 4 mo ago also BIT-typo3-2020-15098 , EUVD-2020-0564 , GHSA-m5vr-3m74-jwxp

cvss
8.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
2.2%
EPSS 2.2% chance of exploitation in 30 days, percentile 82%
public exploits
0
none known

Summary

In TYPO3 CMS greater than or equal to 9.0.0 and less than 9.5.20, and greater than or equal to 10.0.0 and less than 10.4.6, it has been discovered that an internal verification mechanism can be used to generate arbitrary checksums. This allows to inject arbitrary data having a valid cryptographic message authentication code (HMAC-SHA1) and can lead to various attack chains including potential privilege escalation, insecure deserialization & remote code execution. The overall severity of this vulnerability is high based on mentioned attack chains and the requirement of having a valid backend user session (authenticated). This has been patched in versions 9.5.20 and 10.4.6.

Patch / fix

  • packagist typo3/cms-core 9.5.20, 10.4.6
  • packagist typo3/cms 9.5.20, 10.4.6
  • bitnami typo3 9.5.20, 10.4.6
  • typo3 typo3 9.5.20, 10.4.6

Exploit prediction

2.23% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

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

Affected packages

ecosystem package affected fixed in
packagist typo3/cms-core
>=9.0.0, <9.5.20
>=10.0.0, <10.4.6
9.5.20
10.4.6
packagist typo3/cms
>=10.0.0, <10.4.6
>=9.0.0, <9.5.20
10.4.6
9.5.20
bitnami typo3
>=9.0.0, <9.5.20
>=10.0.0, <10.4.6
9.5.20
10.4.6

Affected products

  • TYPO3 TYPO3 CMS

Classification

Weakness
  • CWE-325 Missing Cryptographic Step
  • CWE-20 Improper Input Validation
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
  • CWE-502 Deserialization of Untrusted Data
  • CWE-327 Use of a Broken or Risky Cryptographic Algorithm

References

Sources

Fencer Vulns 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.