CVE-2024-43118

Hummingbird <= 3.9.1 - Missing Authorization

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-862 · Missing Authorization
CVE
CVE-2024-43118
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-43118 is a medium-severity Missing Authorization 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). The root cause is a missing authorization check on a reachable function. 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 unauthorized modification of data due to a missing capability check on the clear_module_cache() function in versions up to, and including, 3.9.1. This makes it possible for authenticated attackers, with contributor-level access and above, to clear module cache.

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 interaction from a victim user.

CWE-862: Missing Authorization

Hummingbird Performance <= 3.9.1 carries this weakness at clear_module_cache(), and reaching it takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. 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?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Hummingbird Performance 3.9.2 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-43118https://www.wordfence.com/threat-intel/vulnerabilities/id/a68dac5d-b07b-40c1-aad1-73e2c8d0f927https://nvd.nist.gov/vuln/detail/CVE-2024-43118

Related records

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