# CVE-2024-51793: WordPress RepairBuddy plugin <= 3.8115 - Arbitrary File Upload vulnerability

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

- **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-vw9p-qc5q-j6rw

## What is CVE-2024-51793?

CVE-2024-51793 is a critical vulnerability in Ateeq Rafeeq RepairBuddy, 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 Ateeq Rafeeq RepairBuddy computer-repair-shop allows Upload a Web Shell to a Web Server.This issue affects RepairBuddy: from n/a through <= 3.8115.

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

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

It affects 1 product.


Products: Webfulcreations Computer Repair Shop.

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

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

## Is CVE-2024-51793 being exploited?

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

Public exploit code:

-  WordPress RepairBuddy plugin <= 3.8115 - Arbitrary File Upload vulnerability (github_poc): https://github.com/Nxploited/CVE-2024-51793
- (CVE-2024-51793) Wordpress Plugin: Computer Repair Shop <= 3.8115 - Unauthenticated Arbitrary File Upload (github_poc): https://github.com/KTN1990/CVE-2024-51793
- Unauthenticated 0-click RCE exploit for CVE-2024-51793. Exploits an arbitrary file upload vulnerability via admin-ajax.php to upload a PHP payload and achieve remote command execution on vulnerable WordPress installations, including OS detection and an interactive command shell. (github_poc): https://github.com/JoshuaProvoste/0-click-RCE-Exploit-for-CVE-2024-51793
- https://github.com/0axz-tools/CVE-2024-51793 (github_poc): https://github.com/0axz-tools/CVE-2024-51793

## Fix prompt for AI coding agents

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

What it is: CVE-2024-51793 is a critical vulnerability in Ateeq Rafeeq RepairBuddy, 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-51793 in the wild and no public exploit code.

Affected product: Ateeq Rafeeq RepairBuddy. 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-51793/ (Markdown: https://insights.sbomify.com/CVE-2024-51793/index.md)
```

## Sources

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

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