Skip to content
Fencer Intel
high 8.8

CVE-2019-19849 json

TYPO3 Insecure Deserialization in Query Generator & Query View

published 6y ago modified 4mo ago also GHSA-rcgc-4xfc-564v , EUVD-2022-5150

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

Summary

An issue was discovered in TYPO3 before 8.7.30, 9.x before 9.5.12, and 10.x before 10.2.2. It has been discovered that the classes QueryGenerator and QueryView are vulnerable to insecure deserialization. One exploitable scenario requires having the system extension ext:lowlevel (Backend Module: DB Check) installed, with a valid backend user who has administrator privileges. The other exploitable scenario requires having the system extension ext:sys_action installed, with a valid backend user who has limited privileges.

Patch / fix

  • packagist typo3/cms-core 8.7.30, 9.5.12, 10.2.1
  • packagist typo3/cms 8.7.30, 9.5.12, 10.2.1
  • typo3 typo3 8.7.30, 9.5.12, 10.2.2

Is CVE-2019-19849 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 69% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.0 8.8 CVSS:3.0/AC:L/AV:N/A:H/C:H/I:H/PR:L/S:U/UI:N
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA 3.0 8.8 CVSS:3.0/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
GitHub 3.0 8.8 CVSS:3.0/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
>=10.0.0, <10.2.1
>=8.0.0, <8.7.30
>=9.0.0, <9.5.12
10.2.1
8.7.30
9.5.12
packagist typo3/cms
>=10.0.0, <10.2.1
>=8.0.0, <8.7.30
>=9.0.0, <9.5.12
10.2.1
8.7.30
9.5.12

Classification

Weakness
  • 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.