# CVE-2024-43117: WordPress Hummingbird plugin <= 3.9.1 - Cross Site Request Forgery (CSRF) vulnerability

> Attackers can trick authenticated users into performing unwanted actions in the Hummingbird WordPress plugin, potentially altering site settings.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Aug 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-mx5v-6xw3-6p2w

## What is CVE-2024-43117?

CVE-2024-43117 is a medium-severity vulnerability in WPMU DEV - Your All-in-One WordPress Platform Hummingbird, published on 26 Aug 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Cross-Site Request Forgery (CSRF) vulnerability in WPMU DEV - Your All-in-One WordPress Platform Hummingbird hummingbird-performance.This issue affects Hummingbird: from n/a through <= 3.9.1.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Wpmudev Hummingbird.

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

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

## Is CVE-2024-43117 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-43117 is a medium-severity vulnerability in WPMU DEV - Your All-in-One WordPress Platform Hummingbird, published on 26 Aug 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-43117 in the wild and no public exploit code.

Affected product: WPMU DEV - Your All-in-One WordPress Platform Hummingbird. 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-43117/ (Markdown: https://insights.sbomify.com/CVE-2024-43117/index.md)
```

## Sources

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

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