dbcve.org
ZoneminderApplication

CVE-2025-65791

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
ZoneMinder v1.36.34 is vulnerable to Command Injection in web/views/image.php. The application passes unsanitized user input directly to the exec() function. NOTE: this is disputed by the Supplier because there is no unsanitized user input to web/views/image.php.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

ZoneMinder v1.36.34 contains a command injection vulnerability in web/views/image.php where unsanitized user input is passed directly to the PHP exec() function, allowing remote attackers to execute arbitrary system commands. The supplier disputes this claim, stating there is no unsanitized user input to this file.

MitigationInvestigate the actual code path and user input flow to verify if command injection is possible; if confirmed, implement proper input sanitization and validation before passing any data to exec() or use safer alternatives.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ZoneminderApplication
Affected:= 1.36.34

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm ZoneMinder version
    Run command: zmversion or check /usr/share/zoneminder/VERSION or look at the web interface footer for version number
    Affected if version is exactly 1.36.34 (note: other versions may also be affected if backported)
  2. Locate the affected file
    Find web/views/image.php in your ZoneMinder installation directory, commonly at /usr/share/zoneminder/web/views/image.php or /var/www/html/zoneminder/web/views/image.php
    Affected if file exists at this path in your installation
  3. Inspect the file for exec() calls with user input
    Open the file and search for exec() function calls. Examine if any parameters passed to exec() come from $_GET, $_POST, or $_REQUEST superglobals without sanitization
    Affected if code contains exec() calls that directly use unsanitized user-supplied parameters
  4. Identify the vulnerable parameter flow
    Trace which parameters from the URL (view, capture, etc.) are passed through to the exec() call. Check if these parameters can be controlled by an external attacker
    Affected if user-controllable parameters flow directly to exec() without escaping or validation
  5. Test if the code path is reachable
    Attempt to access the file via web browser with a test parameter (e.g., ?view=test) and observe if the parameter is processed by the vulnerable code path
    Affected if the vulnerable exec() code path executes based on web request parameters

You are affected if running ZoneMinder 1.36.34 AND the web/views/image.php file contains exec() calls that process unsanitized user input from web requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Investigate the actual code path and user input flow to verify if command injection is possible; if confirmed, implement proper input sanitization and validation before passing any data to exec() or use safer alternatives.

Recommended fix Moderate confidence

Latest stable ZoneMinder release (1.36.35+ or 1.37.x)

  1. Check if a newer ZoneMinder release exists that addresses this vulnerability
  2. If available, upgrade to the latest stable release (e.g., 1.36.35 or later, or 1.37.x series)
  3. Review the web/views/image.php file in the new release to confirm the command injection vector has been addressed
  4. Verify the fix by testing the image viewing functionality with various inputs
  5. Monitor ZoneMinder security advisories for any additional updates
Caveat Check release notes for any breaking changes between 1.36.34 and the target version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Zoneminder Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,940
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-65791 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-65791 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data