/

CVE-2026-76060

Severity:

HIGH RISK

(8.8)

OS Command Injection (CWE-78) in ZoneMinder Export

CVE-2026-76060

Deferred

Vulnerability type

Category:

OS Command Injection

CWE:

CWE-78

Impact:

Arbitrary OS Command Execution

Severity:

HIGH RISK

(8.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

ZoneMinder contains an authenticated operating system command injection vulnerability in its event export functionality. An authenticated user with View Events permission may be able to execute arbitrary operating system commands when an export request parameter is incorporated into a shell command without adequate sanitization.

Affected context

The vulnerability occurs in ZoneMinder deployments where the event export endpoint processes the exportFile HTTP request parameter and passes it to a shell command through PHP's exec() function. Risk depends on the endpoint being reachable by an authenticated account with View Events permission and on the application service having sufficient operating system privileges.

Exploit preconditions

  • Attack surface: Authenticated HTTP event export functionality
  • Required access: A valid account with View Events permission
  • Trigger point: Processing of the exportFile request parameter
  • Why exploitation is possible: User-controlled input reaches a shell command without adequate command-boundary enforcement or neutralization

Why this happens

The underlying bug is an OS command injection flaw mapped to CWE-78. The application constructs or invokes a shell command using a request parameter that remains under user influence, allowing shell interpretation to alter the command's intended behavior. Reliance on shell execution for a value that should be treated as data creates an unsafe boundary between web input and operating system operations.

Potential impact

  • An attacker may execute arbitrary commands under the application service account.
  • The attacker could access, alter, or delete files available to that account.
  • The vulnerability may enable modification of exported event data or other application data.
  • A compromised service account could support lateral movement or further host compromise.

General mitigation guidance

Mitigation generally focuses on removing shell interpretation from event

export operations and reducing the trust placed in request parameters.

Common defensive patterns include:

  • Prefer direct process or library APIs that do not invoke a shell.
  • Treat export paths and filenames as data, using strict allowlists and canonicalization.
  • Apply server-side validation tied to the expected export format and destination.
  • Avoid accepting caller-controlled command fragments or executable options.
  • Run the application with a dedicated least-privilege service account.
  • Restrict filesystem, process, and network permissions available to the service.
  • Enforce authorization checks consistently at the export endpoint and related handlers.

How teams detect issues like this

Organizations can look for command injection risks through:

  • Static analysis rules identifying exec(), shell invocation, and string concatenation with request parameters.
  • Code review checks for HTTP input flowing into process execution or file-export commands.
  • Tests that verify export parameters are handled through direct APIs rather than shell parsing.
  • Web application monitoring for unusual event export requests, command metacharacters, or unexpected file paths.
  • Runtime policy enforcement that restricts child-process creation and service-account privileges.

Automated application-security review tools may help identify request-to-command execution paths during development.

Sources

SourceLink
github.comgithub.com/ZoneMinder/zoneminder
github.comgithub.com/ZoneMinder/zoneminder/security/advisories/GHSA-88m4-hrgp-m9v3
github.comgithub.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-237-02.json
cisa.govcisa.gov/news-events/ics-advisories/icsa-26-237-02
zoneminder.comzoneminder.com/downloads

Frequently asked

questions

Exploitation generally requires authentication and an account with View Events permission, plus access to the affected event export functionality.

No. Based on the described access control, an attacker would normally need valid credentials and the required permission. Exposure still depends on deployment configuration and authorization enforcement.

The safest pattern is to eliminate shell execution for export handling and use a dedicated API with strict allowlisted validation for filenames, paths, and export options.

Keep user input separate from operating system commands, apply least privilege to the application service, review all process-spawning code, and monitor endpoint inputs and child-process activity.

Find out what's already
exploitable in your codebase.