HomeWordPress vulnerabilitiesHummingbird Performance
Hummingbird Performance vulnerabilities
Hummingbird Performance has 6 known vulnerabilities in this database. The most recent published record is dated 5 Sep 2026.
- Known vulnerabilities
- 6
- Active installs
- 70,000+
- Latest version
- 3.21.2
- Last updated
- 1 Sep 2026
- Most recent
- 5 Sep 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Remote code execution CVE-2026-83627 | Critical 9.8 | Up to 3.21.0 | Fixed in a later version (latest 3.21.2) | 5 Sep 2026 |
| Remote code execution CVE-2026-19224 | High 7.2 | Before 3.21.2 | Fixed in 3.21.2 | 4 Sep 2026 |
| Sensitive data exposure CVE-2025-14437 | High 7.5 | Up to 3.18.0 | Fixed in a later version (latest 3.21.2) | 18 Dec 2025 |
| Broken access control CVE-2024-43118 | Medium 4.3 | Before 3.9.2 | Fixed in 3.9.2 | 1 Nov 2024 |
| Cross-site request forgery (CSRF) CVE-2024-43117 | Medium 4.3 | Before 3.9.2 | Fixed in 3.9.2 | 26 Aug 2024 |
| Broken access control CVE-2024-32792 | Medium 4.3 | Before 3.7.4 | Fixed in 3.7.4 | 9 Jun 2024 |
Read the published descriptions
- CVE-2026-83627, 5 Sep 2026
- The Hummingbird - Speed Optimization, Caching, Minify, Compress & CDN plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 3.21.0 via the log_msg() function in core/modules/class-page-cache.php. The page-cache debug log is written to wp-content/wphb-logs/page-caching-log.php, a directly web-accessible PHP file that is supposed to be protected by a leading '<?php die(); ?>' header. That header is guarded by class_exists( 'Filesystem' ), which can never match because class_exists() resolves string arguments in the global namespace while the class is Hummingbird\Core\Filesystem; when the log is created during a front-end request the header is therefore omitted entirely. get_cookies() then writes the raw name of any cookie matching the wphb_cache_ prefix into that file without sanitization. This makes it possible for unauthenticated attackers to write arbitrary PHP into the log file with a single anonymous request and execute it by requesting the file directly, resulting in full remote code execution. Exploitation requires the site administrator to have enabled Page Caching with the Debug Log option (non-default), and the log file to be created during a front-end request - a state reached by the plugin's own 'Clear logs' action, any cache flush, or unattended via the plugin's daily log-rotation cron, which can strip the protective header from an existing log file. CVE record
- CVE-2026-19224, 4 Sep 2026
- The Hummingbird Performance WordPress plugin before 3.21.2 does not restrict a network-wide setting to network administrators, allowing an administrator of any single site on a multisite network to execute arbitrary code across the entire network. CVE record
- CVE-2025-14437, 18 Dec 2025
- The Hummingbird Performance plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.18.0 via the 'request' function. This makes it possible for unauthenticated attackers to extract sensitive data including Cloudflare API credentials. CVE record
- CVE-2024-43118, 1 Nov 2024
- Missing 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. CVE record
- CVE-2024-43117, 26 Aug 2024
- 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. CVE record
- CVE-2024-32792, 9 Jun 2024
- Missing 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. CVE record
What to do if you run Hummingbird Performance
If you run Hummingbird Performance, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Hummingbird Performance vulnerabilities
Free. We email you when a new vulnerability is published for Hummingbird Performance, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.