# CVE-2025-3002: Digital China DCME-520 mon_merge_stat_hist.php os command injection

> Remote attackers can execute arbitrary OS commands via the type_name parameter in mon_merge_stat_hist.php on Digital China DCME-520 devices.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/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:** 31 Mar 2025
- **Updated:** 31 Mar 2025
- **Also known as:** GHSA-78f9-wrgm-7qqc

## What is CVE-2025-3002?

CVE-2025-3002 is a medium-severity command injection vulnerability in Digital China DCME-520, published on 31 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability, which was classified as critical, has been found in Digital China DCME-520 up to 20250320. This issue affects some unknown processing of the file /usr/local/WWW/function/audit/newstatistics/mon_merge_stat_hist.php. The manipulation of the argument type_name leads to os command injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. Other parameters might be affected as well.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-77 (Improper Neutralization of Special Elements used in a Command)

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


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

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

## Is CVE-2025-3002 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-3002 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-3002 is a medium-severity command injection vulnerability in Digital China DCME-520, published on 31 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-3002 exists.

Affected product: Digital China DCME-520. 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-3002/ (Markdown: https://insights.sbomify.com/CVE-2025-3002/index.md)
```

## Sources

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

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