CVE-2024-51114
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 · uneditedAn issue in Beijing Digital China Yunke Information Technology Co.Ltd v.7.2.6.120 allows a remote attacker to execute arbitrary code via the code/function/dpi/web_auth/customizable.php file
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 Beijing Digital China Yunke v7.2.6.120 in the web authentication module (customizable.php). The file at code/function/dpi/web_auth/customizable.php does not properly sanitize user input, allowing a remote attacker to inject and 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 the installed version of Beijing Digital China YunkeCheck system information, about page, or version file for the product version number. Look for v7.2.6.120 or comparable version identifier.Affected if The installed version matches or is within the v7.2.6.120 release line.
-
Locate the customizable.php file in the web authentication moduleCheck for the existence of the file at code/function/dpi/web_auth/customizable.php within the web application root directory.Affected if The file code/function/dpi/web_auth/customizable.php exists on the system.
-
Verify the web authentication endpoint is accessibleTest if the customizable.php file is reachable via HTTP/HTTPS requests to the web server. Attempt a benign request to the web_auth endpoint.Affected if The web authentication module (customizable.php) is exposed and accessible via the web interface.
-
Inspect the customizable.php for unsanitized input handlingReview the source code of customizable.php for parameters that accept user input and are passed to system calls, exec, shell_exec, or similar functions without proper sanitization.Affected if The file contains code that passes user-supplied input directly to OS command execution functions without validation.
-
Check web server logs for suspicious requests to customizable.phpReview access logs for requests to customizable.php that contain shell metacharacters (e.g., ;, |, &, $(...), backticks) or unusual parameters that may indicate exploitation attempts.Affected if Log entries show requests to customizable.php with command injection payloads or unexpected parameter patterns.
A system is affected if it runs Beijing Digital China Yunke v7.2.6.120 with the web authentication module accessible and the customizable.php file present containing unsanitized command execution logic.
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 dataRestrict network access to the affected system immediately. If a vendor patch is available, apply it urgently. Otherwise, review the customizable.php file for command injection flaws and implement proper input validation and sanitization before deploying to production.
- 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-51114 — 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-51114 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