CVE-2024-52777
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 · uneditedDCME-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/system/basic/license_update.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 confidenceRemote Code Execution vulnerability in DorCMS (DCME products) license_update.php file allows unauthenticated attackers to execute arbitrary code on affected systems. The vulnerability affects multiple DCME product lines across specific version thresholds.
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<= 9.1.5.11<= 9.3.5.26<= 7.4.12.90<= 9.25.5.11CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify DCME product modelLog into the device admin interface or check device documentation/labels to determine if the device is a Dcnetworks DCME 320, 320-L, 520, or 720 model.Affected if Device is any of these four DCME models.
-
Determine firmware versionCheck the device firmware version through the admin web interface (typically under System > Status or System > About) or via CLI command such as 'show version' or 'fw_printenv'.Affected if Firmware version is at or below 7.4.12.90 (DCME-320), 9.25.5.11 (DCME-520), 9.3.5.26 (DCME-320-L), or 9.1.5.11 (DCME-720).
-
Verify vulnerable endpoint existsAttempt to access the file /function/system/basic/license_update.php via HTTP or HTTPS on the device's web server. Use a tool like curl: curl -v http://TARGET_IP/function/system/basic/license_update.phpAffected if The endpoint responds (any HTTP status code other than 404), indicating the file exists and is accessible.
-
Assess network exposureReview firewall rules, ACLs, or network segmentation to determine if the web interface (port 80/443) is exposed to untrusted networks or the internet.Affected if The device web interface is reachable from untrusted networks without authentication.
If the device is a DCME 320, 320-L, 520, or 720 with firmware at or below the specified thresholds AND the /function/system/basic/license_update.php endpoint is accessible from the network, the system is affected by CVE-2024-52777.
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 dataUpgrade DCME products to versions above 7.4.12.90 (DCME-320), 9.25.5.11 (DCME-520), 9.3.5.26 (DCME-320-L), and 9.1.5.11 (DCME-720). If patching is not immediately feasible, restrict network access to the /function/system/basic/license_update.php endpoint or deploy WAF rules.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-52777 — 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-2024-52777 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