WordPress Hummingbird Plugin Unprotected Log File RCE

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 th

Casky was already ahead

This CVE exploits attack patterns that Casky's 323matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

The Hummingbird WordPress plugin contains a critical Remote Code Execution vulnerability affecting all versions up to 3.21.0. The vulnerability exists in the page-cache debug logging mechanism, where cache logs are written to a web-accessible PHP file (wp-content/wphb-logs/page-caching-log.php) that should be protected by a PHP die() statement. However, this protection relies on a class_exists() check that can never be satisfied, leaving the log file completely unprotected. An attacker can directly access and potentially inject malicious PHP code into this file, achieving arbitrary code execution on the server. This affects millions of WordPress sites using this popular performance optimization plugin, making it a critical supply-chain risk for the WordPress ecosystem.

Casky's 323 mapped security skills detect this vulnerability by correlating two key MITRE ATT&CK techniques: TA0001 (Initial Access) and TA0043 (Reconnaissance). Practitioners using Casky's Claude-powered analysis would observe detection patterns including: (1) suspicious HTTP requests to wp-content/wphb-logs/ directories attempting to access or write to .php files, (2) log file injection attempts where cache parameters contain PHP code payloads, (3) unusual write operations to web-accessible directories followed by subsequent requests to execute those files, and (4) POST requests to page-cache functions with embedded code that bypasses intended filtering. The platform's extended reasoning capabilities help practitioners understand the attack chain—from reconnaissance of the plugin's presence through exploitation of the inadequate class_exists() guard condition—enabling faster incident response and threat hunting across their WordPress infrastructure.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

323 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-83627.

Abuse of Public-Facing API: Mobile API Abuse

mobile security · low

Run

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

MITRE ATT&CK Techniques

TA0001 TA0043

Investigate the attack patterns behind CVE-2026-83627

Casky has 323 skills that investigate the attack patterns behind CVE-2026-83627. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn