dbcve.org
Xm530v200 X6 Weq 8m FirmwareOperating system · Xiongmaitech

CVE-2025-65856

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-22
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
Authentication bypass vulnerability in Xiongmai XM530 IP cameras on Firmware V5.00.R02.000807D8.10010.346624.S.ONVIF 21.06 allows unauthenticated remote attackers to access sensitive device information and live video streams. The ONVIF implementation fails to enforce authentication on 31 critical endpoints, enabling direct unauthorized video stream access.

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 · high confidence

Authentication bypass in Xiongmai XM530 IP camera ONVIF implementation allows unauthenticated access to 31 critical endpoints, exposing device information and live video streams. The vulnerability stems from the ONVIF service failing to enforce authentication checks on these endpoints in firmware V5.00.R02.000807D8.10010.346624.S.ONVIF 21.06.

MitigationApply vendor firmware patch when available; until then, isolate affected cameras on restricted network segments and block external access to ONVIF ports (typically 80, 8080, 8899).

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
Xm530v200 X6 Weq 8m FirmwareOperating system
Affected:= 5.00.r02.000807d8.10010.346624.s.onvif_21.06

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. Identify Xiongmai XM530 cameras on the network
    Scan the network for devices responding to HTTP or ONVIF probes and look for Xiongmaitech or XM530 model identifiers in device responses or UPnP/ONVIF device manifests
    Affected if A Xiongmaitech XM530v200 camera is present on the network with ONVIF service exposed
  2. Check if ONVIF service is enabled and accessible
    Probe typical ONVIF ports (80, 8080, 8899) on identified devices and send an ONVIF GetCapabilities request to determine if the ONVIF service is running
    Affected if The ONVIF service is running and reachable on the camera (ports open and responding to ONVIF requests)
  3. Retrieve the device firmware version
    Use ONVIF GetDeviceInformation or access the camera web interface to query the firmware version. Compare against the affected version: 5.00.r02.000807d8.10010.346624.s.onvif_21.06
    Affected if The camera is running firmware version exactly matching 5.00.r02.000807d8.10010.346624.s.onvif_21.06
  4. Test ONVIF endpoint authentication
    Send unauthenticated ONVIF requests to critical endpoints such as GetDeviceInformation, GetStreamUri, or media endpoints without providing username/password in the WS-Security header
    Affected if The device returns valid responses (device info, stream URIs, or media profiles) without requiring any authentication credentials
  5. Verify sensitive information exposure
    Analyze the unauthenticated responses to confirm they contain device details (model, serial number, firmware) or media stream URIs that should require authentication
    Affected if Device information or live video stream URIs are returned in response to unauthenticated ONVIF requests

A user is affected if they have an Xiongmaitech XM530v200 camera running firmware version 5.00.r02.000807d8.10010.346624.s.onvif_21.06 with the ONVIF service exposed, and the ONVIF endpoints respond to unauthenticated requests with sensitive device information or stream URIs.

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 vendor firmware patch when available; until then, isolate affected cameras on restricted network segments and block external access to ONVIF ports (typically 80, 8080, 8899).

Fix this in Xm530v200 X6 Weq 8m Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-65856 — 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-65856 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