dbcve.org
Dcme 720 FirmwareOperating system · Dcnetworks

CVE-2024-52779

CRITICAL · 9.8 CVSS v3.1 Published 2024-11-29
Fix available
A fix is available. Upgrade to after 9.25.5.11 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
DCME-320 <=7.4.12.90, DCME-520 <=9.25.5.11, DCME-320-L <=9.3.5.26, and DCME-720 <=9.1.5.11 are vulnerable to Remote Code Execution via /function/audit/newstatistics/mon_stat_top10.php.

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 · moderate confidence

DCME network management products contain an unauthenticated Remote Code Execution vulnerability in the /function/audit/newstatistics/mon_stat_top10.php endpoint. The CVSS 9.8 score indicates the vulnerability is network-exploitable, requires no authentication, and has complete impact on confidentiality, integrity, and availability.

MitigationApply vendor patches for the specific product versions if available; otherwise implement network segmentation to restrict access to the affected systems and disable or block access to the vulnerable PHP endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Dcme 720 FirmwareOperating system
Affected:<= 9.1.5.11
Dcme 320 L FirmwareOperating system
Affected:<= 9.3.5.26
Dcme 320 FirmwareOperating system
Affected:<= 7.4.12.90
Dcme 520 FirmwareOperating system
Affected:<= 9.25.5.11

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify DCME product model
    Determine if the target system is a Dcnetworks DCME device (model 720, 320 L, 320, or 520) by checking system information, product label, or administrative interface
    Affected if The system is a Dcnetworks DCME 720, 320 L, 320, or 520 device
  2. Check firmware version for DCME 720
    Access the device administrative interface or firmware management page and locate the firmware version information. Compare against the affected version 9.1.5.11
    Affected if The installed firmware version is 9.1.5.11 or lower on a DCME 720 device
  3. Check firmware version for DCME 320 L
    Access the device administrative interface or firmware management page and locate the firmware version information. Compare against the affected version 9.3.5.26
    Affected if The installed firmware version is 9.3.5.26 or lower on a DCME 320 L device
  4. Check firmware version for DCME 320
    Access the device administrative interface or firmware management page and locate the firmware version information. Compare against the affected version 7.4.12.90
    Affected if The installed firmware version is 7.4.12.90 or lower on a DCME 320 device
  5. Check firmware version for DCME 520
    Access the device administrative interface or firmware management page and locate the firmware version information. Compare against the affected version 9.25.5.11
    Affected if The installed firmware version is 9.25.5.11 or lower on a DCME 520 device
  6. Verify vulnerable endpoint accessibility
    Attempt to access the URL path /function/audit/newstatistics/mon_stat_top10.php on the device from the network. A successful HTTP request to this endpoint indicates the vulnerable component is present
    Affected if The endpoint returns an HTTP response (indicating the PHP file exists and is reachable)

The system is affected if it is a Dcnetworks DCME 720, 320 L, 320, or 520 device running firmware at or below the affected version for its model, and the /function/audit/newstatistics/mon_stat_top10.php endpoint is accessible over the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 9.25.5.11
Interim mitigation

Apply vendor patches for the specific product versions if available; otherwise implement network segmentation to restrict access to the affected systems and disable or block access to the vulnerable PHP endpoint.

Fix this in Dcme 720 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,940
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-52779 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-52779 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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