# CVE-2025-31702: Missing authorization in IPC

> Authenticated users can access admin-restricted data and escalate privileges via specific HTTP requests in Dahua embedded products.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Oct 2025
- **Updated:** 15 Oct 2025
- **Also known as:** GHSA-5x9h-fg8g-wjh2

## What is CVE-2025-31702?

CVE-2025-31702 is a medium-severity missing authorization vulnerability in Dahua IPC, published on 15 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability exists in certain Dahua embedded products. Third-party malicious attacker with obtained normal user credentials could exploit the vulnerability to access certain data which are restricted to admin privileges, such as system-sensitive files through specific HTTP request. This may cause tampering with admin password, leading to privilege escalation. Systems with only admin account are not affected.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2025-31702?


## How do I fix CVE-2025-31702?

No fix has been published for CVE-2025-31702 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-31702 being exploited?

There is no known exploitation of CVE-2025-31702 in the wild and no public exploit code.

Public exploit code:

- Repository with tools, exploits, and material associated with the analysis and discovery process of CVE-2025-31702 and other related security issues. (github_poc): https://github.com/itres-labs/CVE-2025-31702

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-31702 and fix it if it is affected.

What it is: CVE-2025-31702 is a medium-severity missing authorization vulnerability in Dahua IPC, published on 15 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-31702 in the wild and no public exploit code.

Affected product: Dahua IPC. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-31702/ (Markdown: https://insights.sbomify.com/CVE-2025-31702/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-31702
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-31702
- OSV: https://osv.dev/vulnerability/CVE-2025-31702

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-31702/
Summaries are generated and may contain mistakes; the official description above is the record.