# CVE-2026-27470: ZoneMinder: Second-Order SQL Injection in `getNearEvents()` via Stored Event Name and Cause Fields

> Authenticated users can execute arbitrary SQL queries via stored event fields in ZoneMinder, potentially accessing or modifying database contents.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 21 Feb 2026
- **Updated:** 24 Feb 2026
- **Also known as:** DEBIAN-CVE-2026-27470, GHSA-r6gm-478g-f2c4, UBUNTU-CVE-2026-27470

## What is CVE-2026-27470?

CVE-2026-27470 is a high-severity SQL injection vulnerability in Zoneminder Zoneminder, published on 21 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ZoneMinder is a free, open source closed-circuit television software application. In versions 1.36.37 and below and 1.37.61 through 1.38.0, there is a second-order SQL Injection vulnerability in the web/ajax/status.php file within the getNearEvents() function. Event field values (specifically Name and Cause) are stored safely via parameterized queries but are later retrieved and concatenated directly into SQL WHERE clauses without escaping. An authenticated user with Events edit and view permissions can exploit this to execute arbitrary SQL queries.

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

## Which versions are affected by CVE-2026-27470?

It affects 1 product.


Products: Zoneminder Zoneminder.

## How do I fix CVE-2026-27470?

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

## Is CVE-2026-27470 being exploited?

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

Public exploit code:

- ZoneMinder Second-Order SQL Injection PoC — CVE-2026-27470 (github_poc): https://github.com/kocaemre/CVE-2026-27470
- Python PoC for CVE-2026-27470, authenticated second-order SQL injection in ZoneMinder's getNearEvents() (status.php), CVSS 8.8 (github_poc): https://github.com/d3vn0mi/CVE-2026-27470-POC

## Other vulnerabilities in Zoneminder Zoneminder

- [CVE-2008-3882](https://insights.sbomify.com/CVE-2008-3882/): Command injection in n/a (critical 10.0)
- [CVE-2025-65791](https://insights.sbomify.com/CVE-2025-65791/): Command injection in n/a (critical 9.8)
- [CVE-2024-43360](https://insights.sbomify.com/CVE-2024-43360/): ZoneMinder Time-based SQL Injection (critical 9.8)
- [CVE-2022-29806](https://insights.sbomify.com/CVE-2022-29806/): Path traversal in n/a (critical 9.8)
- [CVE-2019-8423](https://insights.sbomify.com/CVE-2019-8423/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-27470 and fix it if it is affected.

What it is: CVE-2026-27470 is a high-severity SQL injection vulnerability in Zoneminder Zoneminder, published on 21 Feb 2026. 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-2026-27470 exists.

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

## Sources

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

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