CVE-2026-27470
Received Received - Intake
Second-Order SQL Injection in ZoneMinder Events Module

Publication date: 2026-02-21

Last updated on: 2026-02-24

Assigner: GitHub, Inc.

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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-21
Last Modified
2026-02-24
Generated
2026-05-07
AI Q&A
2026-02-21
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
zoneminder zoneminder to 1.36.38 (exc)
zoneminder zoneminder From 1.37.61 (inc) to 1.38.1 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2026-27470 is a second-order SQL Injection vulnerability in ZoneMinder, an open source CCTV software. It exists in the getNearEvents() function within the web/ajax/status.php file. Although event fields like Name and Cause are safely stored using parameterized queries, they are later retrieved and concatenated directly into SQL WHERE clauses without proper escaping or parameterization.

This unsafe concatenation allows an authenticated user with Events edit and view permissions to execute arbitrary SQL queries by exploiting the stored event field values.


How can this vulnerability impact me? :

This vulnerability can have severe impacts including compromising the confidentiality, integrity, and availability of the ZoneMinder database.

  • Confidentiality: Attackers can extract arbitrary database content, including sensitive data such as user credentials.
  • Integrity: Attackers can modify data, escalate privileges, or create new administrative accounts by executing arbitrary SQL commands.
  • Availability: Attackers can corrupt or delete database content or cause denial of service by running heavy or malicious queries.

How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

I don't know


What immediate steps should I take to mitigate this vulnerability?

To mitigate the CVE-2026-27470 second-order SQL injection vulnerability in ZoneMinder, the immediate step is to upgrade ZoneMinder to version 1.36.38 or later, where the vulnerability has been fixed.

The fix addresses the unsafe concatenation of stored Event Name and Cause fields into SQL queries by replacing string concatenation with parameterized queries and implementing proper input validation.

Additionally, ensure that only authenticated users with appropriate Events edit and view permissions have access, as exploitation requires such authentication.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart