# CVE-2009-5026: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands in MySQL slave configurations with version mismatches via executable comments.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Aug 2012
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-rw88-9fhw-cqr5

## What is CVE-2009-5026?

CVE-2009-5026 is a medium-severity SQL injection vulnerability in Mysql Mysql, published on 17 Aug 2012. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The executable comment feature in MySQL 5.0.x before 5.0.93 and 5.1.x before 5.1.50, when running in certain slave configurations in which the slave is running a newer version than the master, allows remote attackers to execute arbitrary SQL commands via custom comments.

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

## Which versions are affected by CVE-2009-5026?

It affects 2 products.


Products: Mysql Mysql, Oracle Mysql.

## How do I fix CVE-2009-5026?

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

## Is CVE-2009-5026 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-5026 exists.

Public exploit code:

- Oracle MySQL < 5.1.50 - Privilege Escalation (exploitdb)

## Other vulnerabilities in Mysql Mysql

- [CVE-2004-0627](https://insights.sbomify.com/CVE-2004-0627/): Auth bypass in n/a (critical 10.0)
- [CVE-2004-0628](https://insights.sbomify.com/CVE-2004-0628/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-2446](https://insights.sbomify.com/CVE-2009-2446/): Other in n/a (high 8.5)
- [CVE-2012-0553](https://insights.sbomify.com/CVE-2012-0553/): Memory corruption in n/a (high 7.5)
- [CVE-2013-1492](https://insights.sbomify.com/CVE-2013-1492/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-5026 and fix it if it is affected.

What it is: CVE-2009-5026 is a medium-severity SQL injection vulnerability in Mysql Mysql, published on 17 Aug 2012. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-5026 exists.

Affected product: Mysql Mysql. 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-2009-5026/ (Markdown: https://insights.sbomify.com/CVE-2009-5026/index.md)
```

## Sources

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

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