CVE-2024-52778: 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 R

Q: How do I fix CVE-2024-52778?

dcme-720 firmware: upgrade to newer than 9.1.5.11; dcme-320-l firmware: upgrade to newer than 9.3.5.26; dcme-320 firmware: upgrade to newer than 7.4.12.90. Exact commands for each OS are on this page.

Q: Is CVE-2024-52778 being exploited?

CVE-2024-52778 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-52778 affect?

CVE-2024-52778 affects dcme-720 firmware, dcme-320-l firmware, dcme-320 firmware. Severity is critical (CVSS 9.8). 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_hist.php.

Q: How urgent is CVE-2024-52778?

Priority 53/100. Critical severity; Remotely exploitable, no login, no user action

This month

CRITICAL 9.8REMOTEUPGRADEUPGRADEUPGRADE

CVE-2024-52778 is a critical-severity flaw (CVSS 9.8) affecting dcme-720 firmware, dcme-320-l firmware, dcme-320 firmware. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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_hist.php.

Why this priority

Critical severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.7% (top 46%)
CISA exploited list	No
Published	2024-11-29
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: dcnetworks

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-11-29 16:15 UTCPublished CVE record published
2026-06-17 08:07 UTCUpdated Record last modified

dcnetworks dcme-720 firmware UPGRADE

Affected: <= 9.1.5.11

Fixed in: newer than 9.1.5.11

Safe to downgrade to: no unaffected older release

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

dcnetworks dcme-320-l firmware UPGRADE

Affected: <= 9.3.5.26

Fixed in: newer than 9.3.5.26

Safe to downgrade to: no unaffected older release

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

dcnetworks dcme-320 firmware UPGRADE

Affected: <= 7.4.12.90

Fixed in: newer than 7.4.12.90

Safe to downgrade to: no unaffected older release

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

dcnetworks dcme-520 firmware UPGRADE

Affected: <= 9.25.5.11

Fixed in: newer than 9.25.5.11

Safe to downgrade to: no unaffected older release

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-52778?

dcme-720 firmware: upgrade to newer than 9.1.5.11; dcme-320-l firmware: upgrade to newer than 9.3.5.26; dcme-320 firmware: upgrade to newer than 7.4.12.90. Exact commands for each OS are on this page.

Is CVE-2024-52778 being exploited?

CVE-2024-52778 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-52778 affect?

CVE-2024-52778 affects dcme-720 firmware, dcme-320-l firmware, dcme-320 firmware. Severity is critical (CVSS 9.8). 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_hist.php.

How urgent is CVE-2024-52778?

Priority 53/100. Critical severity; Remotely exploitable, no login, no user action

Software pages

PHP vulnerabilities

Related CVEs

CVE-2025-9387 MEDIUM 6.3 MITIGATE A vulnerability was found in DCN DCME-720 9.1.5.11
CVE-2024-52782 CRITICAL 9.8 UPGRADE UPGRADE 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 R
CVE-2024-52781 CRITICAL 9.8 UPGRADE UPGRADE 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 R
CVE-2024-52780 CRITICAL 9.8 UPGRADE UPGRADE 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 R
CVE-2024-52779 CRITICAL 9.8 UPGRADE UPGRADE 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 R

References

← Back to latest CVEs