CVE-2024-43117: WordPress Hummingbird plugin <= 3.9.1 - Cross Site Request Forgery (CSRF) vulnerability
First published: Mon Aug 26 2024(Updated: )
Cross-Site Request Forgery (CSRF) vulnerability in WPMU DEV Hummingbird.This issue affects Hummingbird: from n/a through 3.9.1.
Credit: audit@patchstack.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| WPMU DEV Hummingbird | <3.9.2 |
Remedy
Update to 3.9.2 or a higher version.
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the severity of CVE-2024-43117?
CVE-2024-43117 is classified as a Cross-Site Request Forgery (CSRF) vulnerability.
How do I fix CVE-2024-43117?
To mitigate CVE-2024-43117, update the WPMU DEV Hummingbird plugin to version 3.9.2 or later.
Which versions of Hummingbird are affected by CVE-2024-43117?
CVE-2024-43117 affects Hummingbird versions prior to 3.9.2.
What are the potential impacts of CVE-2024-43117?
Exploitation of CVE-2024-43117 could allow an attacker to perform unauthorized actions on behalf of authenticated users.
Is CVE-2024-43117 a common vulnerability in WordPress plugins?
CSRF vulnerabilities like CVE-2024-43117 are relatively common in WordPress plugins that do not implement robust security measures.
- agent/title
- agent/weakness
- agent/references
- agent/remedy
- agent/type
- agent/description
- agent/first-publish-date
- agent/author
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/last-modified-date
- agent/event
- agent/softwarecombine
- agent/source
- agent/tags
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/wpmudev
- canonical/wpmu dev hummingbird