# CVE-2010-5049: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands via the nav_time parameter in Zabbix, potentially compromising database integrity and confidentiality.

- **Severity:** High 7.5 (`AV:N/AC:L/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:** Yes
- **Published:** 23 Nov 2011
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2010-5049, GHSA-j62j-v7xw-jfcc

## What is CVE-2010-5049?

CVE-2010-5049 is a high-severity SQL injection vulnerability in Zabbix Zabbix, published on 23 Nov 2011. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SQL injection vulnerability in events.php in Zabbix 1.8.1 and earlier allows remote attackers to execute arbitrary SQL commands via the nav_time parameter.

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

## Which versions are affected by CVE-2010-5049?

It affects 1 product.


Products: Zabbix Zabbix.

## How do I fix CVE-2010-5049?

Upgrade to a fixed version.

## Is CVE-2010-5049 being exploited?

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

## Other vulnerabilities in Zabbix Zabbix

- [CVE-2022-23131](https://insights.sbomify.com/CVE-2022-23131/): Zabbix Frontend Authentication Bypass (critical 9.1, exploited in the wild)
- [CVE-2007-0640](https://insights.sbomify.com/CVE-2007-0640/): Memory corruption in n/a (critical 10.0)
- [CVE-2024-42327](https://insights.sbomify.com/CVE-2024-42327/): SQL injection in user.get API (critical 9.9)
- [CVE-2024-22116](https://insights.sbomify.com/CVE-2024-22116/): Remote code execution within ping script (critical 9.9)
- [CVE-2013-3738](https://insights.sbomify.com/CVE-2013-3738/): Code injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-5049 and fix it if it is affected.

What it is: CVE-2010-5049 is a high-severity SQL injection vulnerability in Zabbix Zabbix, published on 23 Nov 2011. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-5049 in the wild and no public exploit code.

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

## Sources

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

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