PatchSiren cyber security CVE debrief

CVE-2026-83627 wpmudev CVE debrief

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.

Vendor: wpmudev
Product: Hummingbird Performance – Cache & Page Speed Optimization for Core Web Vitals | Critical CSS | Minify CSS | Defer CSS Javascript | CDN
CVSS: CRITICAL 9.8
CISA KEV: Not listed in stored evidence
Original CVE published: 2026-09-05
Original CVE updated: 2026-09-07
Advisory published: 2026-09-05
Advisory updated: 2026-09-07

Who should care

WordPress administrators and security teams should assess exposure of their installations using the Hummingbird plugin, especially those with Page Caching and Debug Log enabled, and prioritize remediation or compensating controls to prevent exploitation.

Why it matters

The Hummingbird plugin for WordPress is vulnerable to Remote Code Execution, allowing unauthenticated attackers to write arbitrary PHP and execute it by requesting the file directly. Defenders should prioritize verifying exposure, remediation, and monitoring to prevent exploitation.

Verify exposure of WordPress installations using the Hummingbird plugin
Remediate by updating to a fixed version or disabling the vulnerable functionality
Monitor for suspicious activity and implement compensating controls to prevent exploitation
Prioritize verification of inventory and remediation of vulnerable instances

Technical summary

The Hummingbird plugin for WordPress is vulnerable to Remote Code Execution due to a weakness in the log_msg() function in core/modules/class-page-cache.php. The page-cache debug log is written to a directly web-accessible PHP file without proper protection, allowing unauthenticated attackers to write arbitrary PHP and execute it by requesting the file directly. This vulnerability requires the site administrator to have enabled Page Caching with the Debug Log option and the log file to be created during a front-end request. Defenders should prioritize verifying exposure of WordPress installations using the Hummingbird plugin, especially those with Page Caching and Debug Log enabled, and remediate by updating to

Defensive priority

Defenders should prioritize verifying exposure of WordPress installations using the Hummingbird plugin, especially those with Page Caching and Debug Log enabled, and remediate by updating to a fixed version or disabling the vulnerable functionality.

Recommended defensive actions

Verify exposure of WordPress installations using the Hummingbird plugin, especially those with Page Caching and Debug Log enabled
Remediate by updating to a fixed version or disabling the vulnerable functionality
Monitor for suspicious activity and implement compensating controls to prevent exploitation
Review compensating controls for exposed systems while remediation is scheduled and verified
Check relevant monitoring, detection, and logs for exposed assets that need extra review
Track exceptions, retest remediated assets, and close the item only after evidence is documented
Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including the affected plugin, version, and exploitation requirements. However, the exact scope of affected installations and the availability of a fixed version require further verification from the official sources.

Sources and references

Verified primary and authoritative sources

CVE-2026-83627 CVE Program record
Publisher, destination, and source semantics verified

URL: https://www.cve.org/CVERecord?id=CVE-2026-83627

CVE Program - Official CVE Program record with source-provided CVE metadata.
CVE-2026-83627 NVD vulnerability detail
Publisher, destination, and source semantics verified

URL: https://nvd.nist.gov/vuln/detail/CVE-2026-83627

NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Source reference
Unverified legacy reference

URL: https://plugins.trac.wordpress.org/browser/hummingbird-performance/trunk/core/modules/class-page-cache.php

[email protected]
Source reference
Unverified legacy reference

URL: https://plugins.trac.wordpress.org/changeset/3675836/hummingbird-performance/trunk/core/modules/class-page-cache.php

[email protected]

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.