# CVE-2024-51792: WordPress Audio Record plugin <= 1.0 - Arbitrary File Upload vulnerability

> Attackers can upload malicious web shells via the Audio Record plugin, leading to remote code execution on the WordPress server.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Nov 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-67c8-xphv-qf8f

## What is CVE-2024-51792?

CVE-2024-51792 is a critical vulnerability in Dang Ngoc Binh Audio Record, published on 11 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unrestricted 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.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2024-51792?


## How do I fix CVE-2024-51792?

No fix has been published for CVE-2024-51792 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-51792 being exploited?

There is no known exploitation of CVE-2024-51792 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-51792 and fix it if it is affected.

What it is: CVE-2024-51792 is a critical vulnerability in Dang Ngoc Binh Audio Record, published on 11 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-51792 in the wild and no public exploit code.

Affected product: Dang Ngoc Binh Audio Record. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-51792/ (Markdown: https://insights.sbomify.com/CVE-2024-51792/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-51792
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-51792
- OSV: https://osv.dev/vulnerability/CVE-2024-51792

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-51792/
Summaries are generated and may contain mistakes; the official description above is the record.