Skip to content
Fencer Intel
medium 4.3

CVE-2010-5104 json

TYPO3 Sensitive Information Disclosure via escapeStrForLike method

published 14y ago modified 4mo ago also GHSA-xgc2-q928-27wv , EUVD-2022-5782

cvss
4.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.6%
EPSS 1.6% chance of exploitation in 30 days, percentile 76%
public exploits
0
none known

Summary

The escapeStrForLike method in TYPO3 4.2.x before 4.2.16, 4.3.x before 4.3.9, and 4.4.x before 4.4.5 does not properly escape input when the MySQL database is set to sql_mode NO_BACKSLASH_ESCAPES, which allows remote attackers to obtain sensitive information via wildcard characters in a LIKE query.

Patch / fix

  • packagist typo3/cms-core 4.2.16, 4.3.9, 4.4.5

Is CVE-2010-5104 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.65% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:P/I:N/A:N

Affected packages

ecosystem package affected fixed in
packagist typo3/cms-core
>=4.2.0, <4.2.16
>=4.3.0, <4.3.9
>=4.4.0, <4.4.5
4.2.16
4.3.9
4.4.5

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

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.