HummingbirdWordPress extension · Incsub
CVE-2024-43118
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMissing Authorization vulnerability in WPMU DEV - Your All-in-One WordPress Platform Hummingbird hummingbird-performance.This issue affects Hummingbird: from n/a through <= 3.9.1.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceMissing Authorization vulnerability in the Hummingbird WordPress plugin (versions <= 3.9.1) allows authenticated users to perform actions without proper capability checks. This Broken Access Control issue likely enables low-privileged users to execute functionality that should be restricted to administrators.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
HummingbirdWordPress extension
< 3.9.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Hummingbird plugin version in WordPress adminGo to Plugins > Installed Plugins > Find Hummingbird by WPMU DEV and note the version number displayedAffected if The version shown is lower than 3.9.2
-
Check version via plugin file headerAccess the WordPress site via FTP or file manager and open wp-content/plugins/hummingbird/includes/class-hummingbird.php, look for 'Version:' in the plugin header commentAffected if The Version field shows a number less than 3.9.2
-
Check version via WP-CLI if availableRun command: wp plugin list --name=hummingbird --format=tableAffected if The version column shows a number less than 3.9.2
-
Verify admin API endpoints are accessibleReview any custom API endpoints or admin AJAX actions added by Hummingbird - check if they properly verify user capabilities using current_user_can() or similar WordPress permission functionsAffected if Any admin actions lack proper capability checks and the plugin version is below 3.9.2
If the installed Hummingbird plugin version is below 3.9.2, the site is affected by this missing authorization vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.9.2
Apply vendor patches when available; until then, restrict backend access to trusted administrator accounts only and monitor for suspicious admin actions.
3.9.2
- Update the Hummingbird plugin to version 3.9.2 or later via the WordPress admin dashboard under Plugins > Installed Plugins
- Navigate to the Hummingbird plugin and select Update Now or check for updates
- Verify the updated version is 3.9.2 or higher after the update completes
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Hummingbird
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-43118 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-43118 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data