# CVE-2025-53703: DuraComm DP-10iN-100-MU Cleartext Transmission of Sensitive Information

> Attackers can intercept sensitive data transmitted in cleartext by DuraComm industrial devices, leading to information disclosure.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jul 2025
- **Updated:** 23 Jul 2025
- **Also known as:** GHSA-r2pr-cmcg-c64r

## What is CVE-2025-53703?

CVE-2025-53703 is a high-severity vulnerability in DuraComm Corporation SPM-500 DP-10iN-100-MU, published on 22 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

DuraComm SPM-500 DP-10iN-100-MU

 transmits sensitive data without encryption over a channel that could be intercepted by attackers.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

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


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

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

## Is CVE-2025-53703 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-53703 is a high-severity vulnerability in DuraComm Corporation SPM-500 DP-10iN-100-MU, published on 22 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-53703 in the wild and no public exploit code.

Affected product: DuraComm Corporation SPM-500 DP-10iN-100-MU. 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-53703/ (Markdown: https://insights.sbomify.com/CVE-2025-53703/index.md)
```

## Sources

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

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