# CVE-2019-9053: SQL injection in n/a

> Unauthenticated attackers can execute blind time-based SQL injection via the News module to read database contents.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Mar 2019
- **Updated:** 17 Nov 2025
- **Also known as:** GHSA-rrqg-2h39-2567

## What is CVE-2019-9053?

CVE-2019-9053 is a high-severity SQL injection vulnerability in Cmsmadesimple Cms Made Simple, published on 26 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2019-9053?

It affects 1 product.


Products: Cmsmadesimple Cms Made Simple.

## How do I fix CVE-2019-9053?

No fix has been published for CVE-2019-9053 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-9053 being exploited?

There is no known exploitation of CVE-2019-9053 in the wild and no public exploit code.

Public exploit code:

- CVE-2019-9053 Exploit for Python 3 (github_poc): https://github.com/4nner/CVE-2019-9053
- The exploit is edited to work with different text encodings and Python 3 and is compatible with CMSMS version 2.2.9 and below. (github_poc): https://github.com/Mahamedm/CVE-2019-9053-Exploit-Python-3
- 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). (github_poc): https://github.com/Dh4nuJ4/SimpleCTF-UpdatedExploit
- https://github.com/ELIZEUOPAIN/CVE-2019-9053-CMS-Made-Simple-2.2.10---SQL-Injection-Exploit (github_poc): https://github.com/ELIZEUOPAIN/CVE-2019-9053-CMS-Made-Simple-2.2.10---SQL-Injection-Exploit
- https://github.com/h3x0v3rl0rd/CVE-2019-9053 (github_poc): https://github.com/h3x0v3rl0rd/CVE-2019-9053
- https://github.com/Azrenom/CMS-Made-Simple-2.2.9-CVE-2019-9053 (github_poc): https://github.com/Azrenom/CMS-Made-Simple-2.2.9-CVE-2019-9053

## Other vulnerabilities in Cmsmadesimple Cms Made Simple

- [CVE-2010-4663](https://insights.sbomify.com/CVE-2010-4663/): Other in n/a (critical 10.0)
- [CVE-2024-1527](https://insights.sbomify.com/CVE-2024-1527/): Unrestricted Upload of File with Dangerous Type in CMS Made Simple (critical 9.8)
- [CVE-2018-10081](https://insights.sbomify.com/CVE-2018-10081/): Auth bypass in n/a (critical 9.8)
- [CVE-2018-10085](https://insights.sbomify.com/CVE-2018-10085/): Deserialization in n/a (critical 9.8)
- [CVE-2017-1000453](https://insights.sbomify.com/CVE-2017-1000453/): Code injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-9053 and fix it if it is affected.

What it is: CVE-2019-9053 is a high-severity SQL injection vulnerability in Cmsmadesimple Cms Made Simple, published on 26 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-9053 in the wild and no public exploit code.

Affected product: Cmsmadesimple Cms Made Simple. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-9053/ (Markdown: https://insights.sbomify.com/CVE-2019-9053/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-9053
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-9053
- OSV: https://osv.dev/vulnerability/CVE-2019-9053

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-9053/
Summaries are generated and may contain mistakes; the official description above is the record.