HummingbirdWordPress extension · Incsub
CVE-2024-32792
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.7.3.
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 WPMU DEV Hummingbird WordPress plugin allows attackers to potentially access functionality without proper permission checks. The vulnerability exists in versions up to and including 3.7.3, where authorization controls are not correctly enforced on certain actions or API endpoints.
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.7.4CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
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.
-
Locate the Hummingbird plugin installationCheck your WordPress plugins directory for the 'hummingbird' folder, or view the installed plugins list in WordPress admin under Plugins > Installed PluginsAffected if The Hummingbird plugin by Incsub/WPMU DEV is present on the site
-
Identify the installed version numberOpen the main Hummingbird plugin file (typically/hummingbird.php) and locate the 'Version:' header in the file comment block, or check the WordPress plugins admin page for the version number displayedAffected if The version shown is 3.7.3 or lower (any version before 3.7.4)
-
Verify the vulnerability is presentSince this is a missing authorization vulnerability affecting versions before 3.7.4, if your installed version is below 3.7.4, the vulnerable code is presentAffected if Version is less than 3.7.4
You are affected if the Hummingbird plugin is installed and the version is anything less than 3.7.4, as authorization checks are not properly enforced on certain actions or API endpoints in those versions.
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.7.4
Update to the patched version of Hummingbird (3.7.4 or later) if available, or implement proper capability checks and nonce verification on all sensitive endpoints within the plugin.
3.7.4
- 1. Backup your WordPress site before performing any updates.
- 2. Navigate to the WordPress admin dashboard.
- 3. Go to Plugins > Installed Plugins.
- 4. Find Hummingbird by WPMU DEV in the plugins list.
- 5. If an update is available, click 'Update Now' to update to version 3.7.4.
- 6. Alternatively, navigate to Hummingbird > Settings > Advanced and check for updates, or manually upload version 3.7.4 from the WordPress repository.
- 7. Verify the update was successful by checking the plugin version in Plugins > Installed Plugins.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Hummingbird
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-32792 — 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-32792 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