CVE-2024-43117: WordPress Hummingbird plugin <= 3.9.1 - Cross Site Request Forgery (CSRF) vulnerability
Published Aug 26, 2024
·Updated
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.
Affected Software
1 affected component
wpmudev Hummingbird Wordpress<3.9.2
Remediation
Information
Update to 3.9.2 or a higher version.
Event History
Aug 26, 2024
CVE Published
via MITRE·08:50 PM
Data Sourced
via MITRE·08:50 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:15 PM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2024-43117?
CVE-2024-43117 is classified as a Cross-Site Request Forgery (CSRF) vulnerability.
2
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.
3
Which versions of Hummingbird are affected by CVE-2024-43117?
CVE-2024-43117 affects Hummingbird versions prior to 3.9.2.
4
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.
5
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.