CVE-2024-43117: Cross-Site Request Forgery (CSRF) vulnerability in WPMU DEV - Your All-in-One WordPress Platform Hummingbird h

Q: How do I fix CVE-2024-43117?

hummingbird: upgrade to 3.9.2. Exact commands for each OS are on this page.

Q: Is CVE-2024-43117 being exploited?

CVE-2024-43117 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-43117 affect?

CVE-2024-43117 affects hummingbird. Severity is medium (CVSS 4.3). 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.

Q: How urgent is CVE-2024-43117?

Priority 18/100. No elevated risk signals yet.

Routine

MEDIUM 4.3UPGRADE

CVE-2024-43117 is a medium-severity flaw (CVSS 4.3) affecting hummingbird. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	4.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.2% (top 89%)
CISA exploited list	No
Weakness	CWE-352
Published	2024-08-26
Last modified	2026-06-17

Publisher (CNA): Patchstack · Vendor: wpmudev

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-08-26 21:15 UTCPublished CVE record published
2026-06-17 07:50 UTCUpdated Record last modified

wpmudev hummingbird UPGRADE

Affected: < 3.9.2

Fixed in: 3.9.2

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy hummingbird || rpm -q hummingbird || hummingbird --version

2. UPGRADE to 3.9.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade hummingbird

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade hummingbird

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-43117?

hummingbird: upgrade to 3.9.2. Exact commands for each OS are on this page.

Is CVE-2024-43117 being exploited?

CVE-2024-43117 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-43117 affect?

CVE-2024-43117 affects hummingbird. Severity is medium (CVSS 4.3). 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.

How urgent is CVE-2024-43117?

Priority 18/100. No elevated risk signals yet.

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2024-43118 MEDIUM 4.3 UPGRADE Missing Authorization vulnerability in WPMU DEV - Your All-in-One WordPress Platform Hummingbird hummingbird-p
CVE-2024-32792 MEDIUM 4.3 UPGRADE Missing Authorization vulnerability in WPMU DEV - Your All-in-One WordPress Platform Hummingbird hummingbird-p

References

← Back to latest CVEs