# CVE-2024-37942: WordPress BerqWP plugin <= 1.7.5 - Unauthenticated Non-Blind Server Side Request Forgery (SSRF) vulnerability

> Unauthenticated attackers can exploit a Server-Side Request Forgery flaw in the BerqWP WordPress plugin to access internal resources.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jul 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-v78r-chcj-pp8v

## What is CVE-2024-37942?

CVE-2024-37942 is a high-severity server-side request forgery vulnerability in Berqier Ltd BerqWP, published on 22 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Server-Side Request Forgery (SSRF) vulnerability in Berqier Ltd BerqWP.This issue affects BerqWP: from n/a through 1.7.5.

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 1 product.


Products: Berqier Berqwp.

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

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

## Is CVE-2024-37942 being exploited?

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

## Other vulnerabilities in Berqier Ltd BerqWP

- [CVE-2024-9344](https://insights.sbomify.com/CVE-2024-9344/): Cross-site scripting in BerqWP – Automated All-In-One Page Speed Optimization for Core Web Vitals, Cache, CDN, Images, CSS, and JavaScript (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-37942 is a high-severity server-side request forgery vulnerability in Berqier Ltd BerqWP, published on 22 Jul 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-37942 in the wild and no public exploit code.

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

## Sources

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

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