CVE-2019-9053

HIGHNVD 8.18.7▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.7 because EPSS predicts 69% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs). NVD baseline CVSS 8.1 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Elevated
8.7EG
EchelonGraph verdictMitigate this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 69%
CISA-KEV: Not listedEPSS PROB: 69%CVSS: 8.1Exploit: Elevated riskExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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.

CVSS v3
8.1
EG Score
8.7HIGHhigh confidence
EG Risk
71
EG Risk 71/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity87% × 45%
Exploitation69% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
69%
EPSS %ILE
99th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (EG-KEV: elevated) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

March 26, 2019

Last Modified

November 17, 2025

Advisory Details (5)

Auto-updated Sep 18, 2026
🔬 Proof of concept available. No fix on record yet.
generic🟡 PoC Available

CMS Made Simple < 2.2.10 - SQL Injection - PHP webapps Exploit

https://www.exploit-db.com/exploits/46635/
generic

Announcing CMS Made Simple v2.2.10 - Spuzzum : : CMS Made Simple

https://www.cmsmadesimple.org/2019/03/Announcing-CMS-Made-Simple-v2.2.10-Spuzzum
generic

CMS Made Simple™ Newsletter - News

https://newsletter.cmsmadesimple.org/w/89247Qog4jCRCuRinvhsofwg
generic

CVE-2019-9053-working-/exploit.py at main · Perseus99999/CVE-2019-9053-working- · GitHub

https://github.com/Perseus99999/CVE-2019-9053-working-/blob/main/exploit.py

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 3× in last 7d / 18× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-03 14:22 UTCEPSS rescore
  2. 2026-09-30 14:59 UTCEPSS rescore
  3. 2026-09-30 10:29 UTCEG score recompute▲ 0.20
  4. 2026-09-26 15:54 UTCEPSS rescore
  5. 2026-09-26 00:20 UTCEPSS rescore
  6. 2026-09-24 13:59 UTCEPSS rescore
  7. 2026-09-22 14:43 UTCEPSS rescore
  8. 2026-09-21 20:28 UTCEPSS rescore
  9. 2026-09-20 20:11 UTCEPSS rescore
  10. 2026-09-18 19:23 UTCEPSS rescore
  11. 2026-09-17 19:22 UTCEPSS rescore
  12. 2026-09-16 14:04 UTCEPSS rescore
  13. 2026-09-15 03:06 UTCEPSS rescore
  14. 2026-09-13 16:42 UTCEPSS rescore
  15. 2026-09-12 14:56 UTCEPSS rescore
  16. 2026-09-11 14:48 UTCEPSS rescore
  17. 2026-09-08 21:55 UTCEPSS rescore
  18. 2026-09-06 13:44 UTCEPSS rescore
  19. 2026-09-05 15:24 UTCEPSS rescore
  20. 2026-09-02 14:08 UTCEPSS rescore
  21. 2026-08-30 01:18 UTCEPSS rescore
  22. 2026-08-26 14:42 UTCEPSS rescore
  23. 2026-08-19 17:00 UTCEPSS rescore
  24. 2026-08-17 13:43 UTCEPSS rescore
  25. 2026-08-15 01:26 UTCEPSS rescore
Show 72 more
  1. 2026-08-13 21:57 UTCEPSS rescore
  2. 2026-08-12 13:47 UTCEPSS rescore
  3. 2026-08-09 13:43 UTCEPSS rescore
  4. 2026-08-08 16:33 UTCEPSS rescore
  5. 2026-08-07 16:23 UTCEPSS rescore
  6. 2026-08-05 19:13 UTCEPSS rescore
  7. 2026-08-03 10:32 UTCEPSS rescore
  8. 2026-08-01 04:12 UTCEPSS rescore
  9. 2026-07-30 16:24 UTCEPSS rescore
  10. 2026-07-30 01:27 UTCEPSS rescore
  11. 2026-07-28 15:32 UTCEPSS rescore
  12. 2026-07-26 14:51 UTCEPSS rescore
  13. 2026-07-25 14:14 UTCEPSS rescore
  14. 2026-07-24 14:14 UTCEPSS rescore
  15. 2026-07-23 14:15 UTCEPSS rescore
  16. 2026-07-23 01:47 UTCEG score recompute▲ 0.40
  17. 2026-07-22 22:30 UTCEG score recompute▼ 0.90
  18. 2026-07-22 14:05 UTCEPSS rescore
  19. 2026-07-21 15:22 UTCEPSS rescore
  20. 2026-07-21 15:22 UTCEPSS rescore
  21. 2026-07-20 17:04 UTCEPSS rescore
  22. 2026-07-19 14:28 UTCEPSS rescore
  23. 2026-07-19 14:28 UTCEPSS rescore
  24. 2026-07-19 02:26 UTCEPSS rescore
  25. 2026-07-19 02:26 UTCEPSS rescore
  26. 2026-07-16 16:59 UTCEPSS rescore
  27. 2026-07-16 16:59 UTCEPSS rescore
  28. 2026-07-15 16:55 UTCEPSS rescore
  29. 2026-07-13 22:27 UTCEPSS rescore
  30. 2026-07-13 22:27 UTCEPSS rescore
  31. 2026-07-13 06:10 UTCEPSS rescore
  32. 2026-07-13 06:10 UTCEPSS rescore
  33. 2026-07-12 05:44 UTCEPSS rescore
  34. 2026-07-12 05:43 UTCEPSS rescore
  35. 2026-07-09 19:06 UTCEPSS rescore
  36. 2026-07-08 15:11 UTCEPSS rescore
  37. 2026-07-07 13:43 UTCEPSS rescore
  38. 2026-07-06 02:20 UTCEPSS rescore
  39. 2026-07-06 02:20 UTCEPSS rescore
  40. 2026-07-05 02:27 UTCEPSS rescore
  41. 2026-07-01 15:03 UTCEPSS rescore
  42. 2026-07-01 15:03 UTCEPSS rescore
  43. 2026-06-28 14:04 UTCEPSS rescore
  44. 2026-06-28 04:54 UTCEPSS rescore
  45. 2026-06-28 04:54 UTCEPSS rescore
  46. 2026-06-27 03:06 UTCEPSS rescore
  47. 2026-06-25 13:47 UTCEPSS rescore
  48. 2026-06-25 13:47 UTCEPSS rescore
  49. 2026-06-24 14:03 UTCEPSS rescore
  50. 2026-06-24 14:03 UTCEPSS rescore
  51. 2026-06-23 21:31 UTCEPSS rescore
  52. 2026-06-23 21:31 UTCEPSS rescore
  53. 2026-06-21 01:57 UTCEPSS rescore
  54. 2026-06-21 01:57 UTCEPSS rescore
  55. 2026-06-18 17:50 UTCEPSS rescore
  56. 2026-06-18 17:50 UTCEPSS rescore
  57. 2026-06-17 17:50 UTCEPSS rescore
  58. 2026-06-16 17:50 UTCEPSS rescore
  59. 2026-06-15 17:46 UTCEPSS rescore
  60. 2026-06-13 22:58 UTCEPSS rescore
  61. 2026-06-12 23:09 UTCEPSS rescore
  62. 2026-06-12 23:09 UTCEPSS rescore
  63. 2026-06-11 13:58 UTCEPSS rescore
  64. 2026-06-10 13:19 UTCEPSS rescore
  65. 2026-06-05 22:45 UTCEPSS rescore
  66. 2026-05-31 22:29 UTCEPSS rescore
  67. 2026-05-31 22:29 UTCEPSS rescore
  68. 2026-05-29 13:42 UTCEPSS rescore
  69. 2026-05-27 21:25 UTCEG score recompute
  70. 2026-05-27 21:25 UTCGHSA enrichment
  71. 2026-05-26 13:42 UTCEPSS rescore
  72. 2026-05-24 16:47 UTCEPSS rescore

Publicly available exploits

(9 references)

Working exploit code is in the public domain (8 GitHub PoCs) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCJagdeepSinghCeh/cms-made-simple-python3
    First seen Nov 15, 2025

    Python3-converted exploit and research notes for CMS Made Simple (CVE-2019-9053) — Unauthenticated SQL Injection vulnerability. Includes original PoC, improved Python3 version, usage instructions, and lab testing reference.

    Open source ↗
  • GitHub PoCAzrenom/CMS-Made-Simple-2.2.9-CVE-2019-9053
    First seen Sep 21, 2024
    Open source ↗
  • GitHub PoCDh4nuJ4/SimpleCTF-UpdatedExploit
    First seen Jun 20, 2024

    This script is a modified version of the original exploit by Daniele Scanu which exploits an unauthenticated SQL injection vulnerability in CMS Made Simple <= 2.2.10 (CVE-2019-9053).

    Open source ↗
  • GitHub PoCMahamedm/CVE-2019-9053-Exploit-Python-3
    First seen May 29, 2023

    The exploit is edited to work with different text encodings and Python 3 and is compatible with CMSMS version 2.2.9 and below.

    Open source ↗
  • GitHub PoCELIZEUOPAIN/CVE-2019-9053-CMS-Made-Simple-2.2.10---SQL-Injection-Exploit
    First seen Oct 25, 2022
    Open source ↗
  • GitHub PoC4nner/CVE-2019-9053
    First seen Dec 28, 2021

    CVE-2019-9053 Exploit for Python 3

    Open source ↗
  • GitHub PoCe-renna/CVE-2019-9053
    First seen Dec 28, 2021

    CVE-2019-9053 Exploit for Python 3

    Open source ↗
  • GitHub PoCh3x0v3rl0rd/CVE-2019-9053
    First seen Jul 18, 2021
    Open source ↗
  • Exploit-DBEDB-46635
    First seen Apr 2, 2019

    CMS Made Simple < 2.2.10 - SQL Injection

    Open source ↗

Frequently asked(5)

What is CVE-2019-9053?
CVE-2019-9053 is a high vulnerability published on March 26, 2019. 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.
When was CVE-2019-9053 disclosed?
CVE-2019-9053 was first published on March 26, 2019, with the most recent update on November 17, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-9053 actively exploited?
CVE-2019-9053 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 69% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2019-9053?
CVE-2019-9053 has a CVSS v3 base score of 8.1 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.7 (HIGH).
How do I remediate CVE-2019-9053?
No fix for CVE-2019-9053 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2019-9053

Explore →

Is Your Infrastructure Affected by CVE-2019-9053?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.