CVE-2024-51792
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 · uneditedUnrestricted Upload of File with Dangerous Type vulnerability in Dang Ngoc Binh Audio Record audio-record allows Upload a Web Shell to a Web Server.This issue affects Audio Record: from n/a through <= 1.0.
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 confidenceThe Audio Record application by Dang Ngoc Binh has an unrestricted file upload vulnerability that allows attackers to upload dangerous file types (web shells) to the web server. This enables remote code execution and complete server compromise.
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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 if Audio Record application is presentSearch for files or directories related to 'Audio Record' or 'Dang Ngoc Binh' on the web server. Check for uploaded application files, web root directories, or any audio recording web application.Affected if The Audio Record application by Dang Ngoc Binh is installed on the server.
-
Locate the file upload endpointReview the application source code or web traffic to identify the upload form, API endpoint, or handling script used for audio file uploads.Affected if An upload endpoint exists and is accessible via HTTP/HTTPS.
-
Check for file type validationInspect the upload handling code to determine if file type validation exists and whether it uses an allowlist approach or merely checks file extensions.Affected if The upload function lacks proper file type validation or relies solely on client-side/file extension checks without content verification.
-
Verify upload directory configurationExamine the web server configuration and upload directory to check if script execution is disabled and if uploads are stored inside or outside the web root.Affected if Uploaded files are stored within the web root and script execution is permitted in that directory.
-
Test for unrestricted upload capabilityIf authorized, attempt to upload a file with a dangerous extension (such as .php, .jsp, .asp) to see if the server accepts it.Affected if The server accepts and stores files with executable extensions without blocking them.
A user is affected if the Audio Record application is installed and its upload functionality permits executable file types to be uploaded to a web-accessible location.
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 dataImplement strict allowlist-based file type validation, verify file content/magic bytes, store uploads outside the web root, rename uploaded files, and disable script execution in the upload directory.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-51792 — 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-51792 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