Skip to content
Fencer Intel
high 8.1

CVE-2019-9053 in the critical feed json

An issue was discovered in CMS Made Simple 2.2.8.

published 7y ago modified 4mo ago also EUVD-2019-18439

cvss
8.1
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
68.6%
EPSS 68.6% chance of exploitation in 30 days, percentile 99.3%
public exploits
1
Exploit-DB

Summary

An issue was discovered in CMS Made Simple 2.2.8. It is possible with the News module, through a crafted URL, to achieve unauthenticated blind time-based SQL injection via the m1_idlist parameter.

Is CVE-2019-9053 in your stack? 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

Timeline

  1. Published
  2. First public exploit (EDB-46635)

Exploit prediction

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

Exploits and checks

  • EDB-46635 CMS Made Simple < 2.2.10 - SQL Injection webapps, 2019-04-02
  • packetstormsecurity.com http://packetstormsecurity.com/files/152356/CMS-Made-Simple-SQL-Injection.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 8.1 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P

Classification

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

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.