CVE-2025-0836
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 · uneditedMissing Authorization vulnerability in Milestone Systems XProtect VMS allows users with read-only access to Management Server to have full read/write access to MIP Webhooks API.
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 confidenceThis is a broken access control vulnerability where the MIP Webhooks API in Milestone Systems XProtect VMS fails to properly enforce authorization checks. Users granted read-only permissions to the Management Server can bypass these restrictions and obtain full read/write access to the Webhooks API, allowing them to create, modify, or delete webhook configurations they should not be permitted to touch.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Identify XProtect VMS versionCheck the installed version of Milestone XProtect VMS via the Management Server or installer informationAffected if Running any version of XProtect VMS that includes the MIP Webhooks API feature
-
Verify MIP Webhooks API is enabledInspect the Management Server configuration or logs to confirm the MIP Webhooks API module is installed and activeAffected if The MIP Webhooks API module is present and running on the Management Server
-
Identify read-only user accountsReview user accounts in the Management Server that are assigned read-only permissions at the server levelAffected if There exist users granted read-only permission tier on the Management Server
-
Test Webhooks API access from read-only accountUsing a read-only user account, attempt a POST, PUT, or DELETE request to the MIP Webhooks API endpoint (e.g., /api/webhooks or similar endpoint)Affected if A read-only user can successfully create, modify, or delete webhook configurations via the API
-
Audit webhook configurations for unauthorized changesReview webhook configuration audit logs or compare current webhooks against known-good baseline to identify changes made by read-only usersAffected if Webhook configurations show modifications authored by read-only permission accounts
A user is affected if their XProtect VMS deployment has the MIP Webhooks API enabled and any read-only permission user can successfully perform write operations (create/modify/delete) against the Webhooks API.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement proper authorization validation in the MIP Webhooks API to enforce the read-only permissions assigned to users at the Management Server level, ensuring all API write operations validate the user's actual permission tier before execution.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2025-0836 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-0836 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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