TYPO3 SQL Injection in low-level Query Generator

published 2019-12-17 6y ago modified 2026-06-17 4mo ago also GHSA-59pj-7mjh-4465 , EUVD-2022-2553

cvss: 5.5; version 3.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.9%; EPSS 0.9% chance of exploitation in 30 days, percentile 59%
public exploits: 0; none known

An issue was discovered in TYPO3 before 8.7.30, 9.x before 9.5.12, and 10.x before 10.2.2. Because escaping of user-submitted content is mishandled, the class QueryGenerator is vulnerable to SQL injection. Exploitation requires having the system extension ext:lowlevel installed, and a valid backend user who has administrator privileges.

Patch / fix

fixed in 3

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

Is CVE-2019-19850 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

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

CVSS scores

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

Affected packages

ecosystem	package	affected	fixed in
packagist	typo3/cms	>=8.0, <8.7.30 >=9.0, <9.5.12 >=10.0, <10.2.2	8.7.30 9.5.12 10.2.2
packagist	typo3/cms-core	>=8.0, <8.7.30 >=9.0, <9.5.12 >=10.0, <10.2.2	8.7.30 9.5.12 10.2.2

Classification

Weakness

CWE-89 Improper Neutralization of Special Elements used in an SQL Command

References

typo3.org /security/advisory/typo3-core-sa-2019-025/
vendor-advisory
review.typo3.org /q/%2522Resolves:+%252389452%2522+topic:security
web, vendor-advisory
nvd.nist.gov /vuln/detail/CVE-2019-19850
advisory
github.com /TYPO3/typo3
package
typo3.org /security/advisory/typo3-core-sa-2019-025
web

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.