CVE-2024-43117

Hummingbird <= 3.9.1 - Cross-Site Request Forgery

2024-08-07 00:00
Rafie Muhammad

Strategic Overview

Status
Patched in 3.9.2
Affected Plugin
Hummingbird Performance – Cache & Page Speed Optimization for Core Web Vitals | Critical CSS | Minify CSS | Defer CSS Javascript | CDN
Affected Version
<= 3.9.1
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-43117
View all Hummingbird Performance – Cache & Page Speed Optimization for Core Web Vitals | Critical CSS | Minify CSS | Defer CSS Javascript | CDN vulnerabilities

At a glance

CVE-2024-43117 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Hummingbird Performance WordPress plugin, affecting versions <= 3.9.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.9.2; sites on affected versions should update now. Disclosed August 2024, reported by Rafie Muhammad.

Vulnerability Overview

The Hummingbird plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.9.1. This is due to missing or incorrect nonce validation on the on_load and maybe_clear_all_cache functions. This makes it possible for unauthenticated attackers to update settings and clear cache via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

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

Reaching this weakness in Hummingbird Performance <= 3.9.1 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Hummingbird Performance the fix is 3.9.2: builds <= 3.9.1 are affected, anything from 3.9.2 onward is not.

Remediation

Update to version 3.9.2, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Hummingbird Performance: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Hummingbird Performance 3.9.2 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-43117https://www.wordfence.com/threat-intel/vulnerabilities/id/4e03b0b9-861d-4909-8608-6378cd0b9176https://nvd.nist.gov/vuln/detail/CVE-2024-43117

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C