# CVE-2024-43160: WordPress BerqWP plugin <= 1.7.6 - Unauthenticated Arbitrary File Upload vulnerability

> Unauthenticated attackers can upload arbitrary files to the BerqWP WordPress plugin, leading to 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:** 13 Aug 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-7g53-9qw7-jg2j

## What is CVE-2024-43160?

CVE-2024-43160 is a critical vulnerability in BerqWP, published on 13 Aug 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 BerqWP allows Code Injection.This issue affects BerqWP: from n/a through 1.7.6.

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

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


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

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

## Is CVE-2024-43160 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-43160 exists.

Public exploit code:

- The BerqWP – Automated All-In-One PageSpeed Optimization Plugin for Core Web Vitals, Cache, CDN, Images, CSS, and JavaScript plugin for WordPress is vulnerable to arbitrary file uploads (github_poc): https://github.com/KTN1990/CVE-2024-43160
- BerqWP <= 1.7.6 - Arbitrary File Upload (nuclei): http/cves/2024/CVE-2024-43160.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2024-43160 is a critical vulnerability in BerqWP, published on 13 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-43160 exists.

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

## Sources

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

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