CVE-2025-3002
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOS command injection vulnerability in Digital China DCME-520 network device firmware. The PHP script /usr/local/WWW/function/audit/newstatistics/mon_merge_stat_hist.php does not properly sanitize the type_name parameter before passing it to a system call, allowing remote attackers to execute arbitrary OS commands.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the device's web interface or check the device label/serial number to confirm it is a Digital China DCME-520 network deviceAffected if The device is NOT a Digital China DCME-520 model - if it is a different model, this CVE does not apply
-
Locate the vulnerable PHP scriptCheck if the file /usr/local/WWW/function/audit/newstatistics/mon_merge_stat_hist.php exists on the device firmware or web rootAffected if The vulnerable PHP script does NOT exist on the device - if absent, the specific flaw cannot be exploited
-
Check firmware version if accessibleIf you can access the device firmware or administrative interface, compare the installed firmware version against any vendor release notes for DCME-520Affected if You cannot determine the firmware version OR the version is newer than any patched release the vendor may issue for this CVE
-
Verify web interface accessibilityConfirm whether the device's web management interface (HTTP/HTTPS) is accessible from the network. Attempt to access the vulnerable script path via browser or curlAffected if The web interface is completely inaccessible from your network segment (isolated/air-gapped) - remote exploitation requires network access to the web service
-
Check if the type_name parameter is acceptedSend a test request to the vulnerable endpoint with a benign type_name value (e.g., ?type_name=test) and observe if the parameter is processed or triggers any responseAffected if The script responds to type_name parameter requests, indicating the vulnerable code path is active
You are affected if you have a Digital China DCME-520 device with the vulnerable PHP script present and its web management interface is network-accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImmediately restrict network access to the device's web interface. If possible, disable or restrict access to the vulnerable PHP script until a vendor patch is available. Implement input validation and use parameterized commands instead of shell execution.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3002 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-3002 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data