Dahua NVR2-4KS3/XVR4232AN-I/T/XVR1B16H-I authentication bypass
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Dahua NVR2-4KS3, XVR4232AN-I, T and XVR1B16H-I. This issue affects some unknown processing. The manipulation leads to authentication bypass. This vulnerability is traded as CVE-2025-31703. It is possible to launch the attack on the physical device. There is no exploit available.
Details
A vulnerability was found in Dahua NVR2-4KS3, XVR4232AN-I, T and XVR1B16H-I (the affected version is unknown) and classified as problematic. This issue affects an unknown code. The manipulation with an unknown input leads to a authentication bypass vulnerability. Using CWE to declare the problem leads to CWE-305. The authentication algorithm is sound, but the implemented mechanism can be bypassed as the result of a separate weakness that is primary to the authentication error. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
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.
The advisory is shared at dahuasecurity.com. The identification of this vulnerability is CVE-2025-31703 since 04/01/2025. The exploitation is known to be easy. An attack has to be approached locally. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-208815). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Authentication bypassCWE: CWE-305 / CWE-287
CAPEC: 🔒
ATT&CK: 🔒
Physical: Yes
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
04/01/2025 CVE reserved03/18/2026 Advisory disclosed
03/18/2026 VulDB entry created
03/22/2026 VulDB entry last update
Sources
Advisory: dahuasecurity.comStatus: Not defined
CVE: CVE-2025-31703 (🔒)
GCVE (CVE): GCVE-0-2025-31703
GCVE (VulDB): GCVE-100-351509
EUVD: 🔒
Entry
Created: 03/18/2026 09:18Updated: 03/22/2026 04:46
Changes: 03/18/2026 09:18 (62), 03/18/2026 11:42 (1), 03/22/2026 04:46 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.