OS Command InjectionWeakness · CWE-78

CVE-2026-3014

CRITICAL · 9.1 CVSS v3.1 Published 2026-07-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable Zero-click 5 weeks old

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
Milestone has released a new version of XProtect® (and several cumulative patch updates) which fix security vulnerability in Management Server API. The vulnerability causes users with edit permissions to the Management Server to be able to execute arbitrary code in context of the Management Server Service.

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

This is an authorization bypass vulnerability in the Milestone XProtect Management Server API where users with edit permissions can execute arbitrary code in the context of the high-privileged Management Server Service. The API fails to properly restrict edit-permission users to intended configuration changes, allowing code execution with service-level privileges.

MitigationApply the vendor patch (new XProtect version or cumulative update) immediately to Management Server; in the interim, audit and restrict users assigned edit permissions to only trusted administrators.

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

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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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. Identify XProtect Management Server installation
    Check for Milestone XProtect Management Server service via Windows Services (services.msc) or by looking for installation directories such as C:\Program Files\Milestone\XProtect Management Server or C:\ProgramData\Milestone\XProtect Management Server
    Affected if The Management Server service is found and running
  2. Determine XProtect version
    Locate the installed version by checking the Management Server about dialog in the XProtect admin interface, or inspect the file version of the Management Server executable (XProtectManagementServer.exe) in the installation directory
    Affected if The installed version has not been patched and falls within the vulnerable version range (verify against vendor release notes)
  3. Verify API exposure
    Check if the XProtect Management Server API endpoints are accessible by attempting to reach the base URL (typically https://servername:443/ManagementServer or similar) or by reviewing IIS/web server bindings on the host
    Affected if The Management Server API is exposed and reachable over the network
  4. Review user roles with edit permissions
    Open the XProtect Management Client or admin console, navigate to Users and Roles, and identify accounts explicitly assigned edit permissions or added to groups with edit-level access
    Affected if Any non-administrator user account possesses edit permissions on the Management Server
  5. Confirm service-level privilege context
    Examine the Management Server Windows service properties to verify it runs under a high-privileged account (such as LocalSystem or a dedicated service account with elevated privileges)
    Affected if The Management Server service runs with elevated privileges and the above conditions (vulnerable version, API accessible, edit-permission users exist) are met

You are affected if XProtect Management Server is running an unpatched version, the API is accessible, and any user with edit permissions exists in the system.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch (new XProtect version or cumulative update) immediately to Management Server; in the interim, audit and restrict users assigned edit permissions to only trusted administrators.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2026-3014 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