F5 Labs June 2026: Honeynet attacks up 55.5%; LiteSpeed Cache CVE-2024-44000 debug.log scanning surges alongside Exchange and PHP exploits
F5 Labs honeynet telemetry shows overall hostile activity rising 55.5% month over month in June 2026, a return to the levels of the earlier-year spike. Highlighted is CVE-2024-44000, an unauthenticated account takeover flaw (CVSS 9.8, CWE-522) in the LiteSpeed Cache WordPress plugin, which rose by 1,128 to 2,603 attacks (#8). Scanning is indiscriminate and comes from a single operation using shared, purpose-built tooling on rented VPS infrastructure. Low-interaction sensors cannot confirm any compromise; the traffic is reconnaissance for readable WordPress debug logs. The Top 10 is led by CVE-2024-4577 (14,706) and CVE-2017-9841 (11,585). CVE-2021-26855 (ProxyLogon) re-entered at #4 and the React Server Components pre-auth RCE CVE-2025-55182 climbed to #5.
Technical Details
- Mechanism: with WordPress debug logging enabled, LiteSpeed Cache (versions up to 6.5.0.1) writes session and cookie data to
/wp-content/debug.log. If that file is web-accessible, an unauthenticated attacker can fetch it, extract a valid session cookie and replay it, gaining administrator access if an admin session is logged. The CVE is not in the CISA KEV catalog, and public PoC code exists. - Scanner behavior: probes
/wp-content/debug.log,/wp-content/uploads/wp-content/debug.log,/logs/wp-content/debug.log,/wordpress/wp-content/debug.logand the rotateddebug.log.1. It also uses URL-encoding evasion (debug%2elog) and cache-busting query strings. - Fingerprints: HTTP/1.0 with
Connection: close, two spoofed User-Agents shared across unrelated IPs, and X-Real-IP/X-Forwarded-For set to the scanner's own IP. Two header-casing variants suggest at least two tool builds. - Co-occurrence: CVE-2005-0869 (phpSysInfo, #9, 1,846 attacks) fires at near-identical per-IP counts, indicating one tool with a broad check library rather than chained exploits.
- Other trends: four Exchange-related CVEs are active (CVE-2021-26855 debuted at #4 with 3,163 attacks, alongside CVE-2022-41082 and CVE-2021-34523). CVE-2025-55182 grew by 1,526 to 3,086. CVE-2025-55184 fell from #7 to #12. Information Leakage events rose 77% to 1,149,567.
- Sources: the US is the top origin (7.73M events), followed by Germany, France and Singapore. China appeared as a new origin with 690,212 events after zero the prior month. Attribution is infrastructure-based only.
- Scanner IPs (top cluster): 5.189.184.50, 2.59.156.103, 144.126.159.74, 103.200.219.112, 195.26.240.180.
Remediation
- Update LiteSpeed Cache beyond 6.5.0.1 and disable debug logging in production; if logging is required, keep the log path non-web-accessible.
- Block external requests to debug.log paths, including nested, rotated and URL-encoded variants. Prefer path-based signatures over IP blocking, since source IPs rotate.
- Rotate WordPress secrets and force re-authentication if a vulnerable version ran with debug logging enabled; audit admin accounts for unexpected sessions or new administrators.
- Verify patch levels for on-premise Exchange (ProxyLogon/ProxyShell), prioritize patching PHP-CGI (CVE-2024-4577), and treat React SSR exposure to CVE-2025-55182 as urgent.
- Use ASN-level filtering rather than blanket geo-blocking of US/DE/FR/SG traffic.
9 exploits públicos
Há código de exploração publicado no Exploit-DB para CVE-2025-55182, CVE-2024-4577, CVE-2024-44000 e outros. O código não é reproduzido aqui: o link leva à fonte, e a explicação foi escrita pela IA a partir do arquivo publicado.
-
React Server 19.2.0 - Remote Code Execution
The script targets CVE-2025-55182, a flaw in how React Server Components deserialize data sent to server function endpoints, as used by frameworks such as Next.js. An unauthenticated attacker with network access to an app running React 19.0.0 to 19.2.0 can trigger it with one crafted POST, no user interaction. It abuses object handling to run JavaScript on the server, giving command execution as the app user. It is a working-looking, blind PoC that scans a target list and leaks command output via DNS lookups; it only prints HTTP status.
-
PHP CGI Module 8.3.4 - Remote Code Execution (RCE)
This script exploits CVE-2024-4577, an argument injection flaw in PHP running as CGI on Windows, where a soft hyphen in the query string is turned into a dash and lets the attacker pass configuration options to the interpreter. It needs only network access to an exposed php-cgi executable, with no login or user interaction. The options make PHP run code sent in the request body, giving command execution as the web server user. It looks like a working exploit with multi-host scanning and an interactive shell.
-
Litespeed Cache 6.5.0.1 - Authentication Bypass
This script targets WordPress sites running LiteSpeed Cache up to 6.5.0.1 (CVE-2024-44000), where debug logging can record request data, including the session cookies of logged-in users. It needs only network access and no login, but the site must have debug logging on and the log file publicly readable. It downloads that log, extracts login cookies per user and lets the attacker pick one to reuse in a browser, enabling account takeover, possibly of an administrator. It looks like a simple working tool, though unverified.
-
PHP Unit 4.8.28 - Remote Code Execution (RCE) (Unauthenticated)
This script exploits CVE-2017-9841: PHPUnit's eval-stdin helper, when left reachable in a web-exposed vendor directory, executes any PHP code sent in an HTTP request body. The attacker needs only network access to a site that deployed PHPUnit (a dev dependency) publicly, with no login or user interaction. The tool checks several common framework layouts with a harmless test, then offers an interactive prompt that runs system commands as the web server user. It is a simple, working exploit that matches the CVE.
-
Microsoft Exchange 2019 - Unauthenticated Email Download (Metasploit)
CVE-2021-26855 · autor: mekhalleh -
Microsoft Exchange 2019 - Unauthenticated Email Download
CVE-2021-26855 · autor: Gonzalo Villegas -
Microsoft Exchange 2019 - Server-Side Request Forgery
CVE-2021-26855 · autor: F5 -
Microsoft Exchange 2019 - Server-Side Request Forgery (Proxylogon) (PoC)
CVE-2021-26855 · autor: testanull -
ThinkPHP - Multiple PHP Injection RCEs (Metasploit)
This Metasploit module exploits remote code execution in the ThinkPHP 5.x web framework through the public index page, where a crafted request makes the framework call a PHP function with attacker-chosen input. The attacker needs only network access to the web server, with no login or user interaction, and a ThinkPHP version up to 5.0.23. The module reads the version from an error page and picks one of two techniques, one per CVE. It runs system commands as the web server user and can drop a Linux payload for a remote session. It is a mature, working exploit.
Linha do tempo
-
F5 Labs June 2026: Honeynet attacks up 55.5%; LiteSpeed Cache CVE-2024-44000 debug.log scanning surges alongside Exchange and PHP exploits
ler a análise desta fonte ocultar
F5 Labs honeynet telemetry shows overall hostile activity rising 55.5% month over month in June 2026, a return to the levels of the earlier-year spike. Highlighted is CVE-2024-44000, an unauthenticated account takeover flaw (CVSS 9.8, CWE-522) in the LiteSpeed Cache WordPress plugin, which rose by 1,128 to 2,603 attacks (#8). Scanning is indiscriminate and comes from a single operation using shared, purpose-built tooling on rented VPS infrastructure. Low-interaction sensors cannot confirm any compromise; the traffic is reconnaissance for readable WordPress debug logs. The Top 10 is led by CVE-2024-4577 (14,706) and CVE-2017-9841 (11,585). CVE-2021-26855 (ProxyLogon) re-entered at #4 and the React Server Components pre-auth RCE CVE-2025-55182 climbed to #5.
Technical Details
- Mechanism: with WordPress debug logging enabled, LiteSpeed Cache (versions up to 6.5.0.1) writes session and cookie data to
/wp-content/debug.log. If that file is web-accessible, an unauthenticated attacker can fetch it, extract a valid session cookie and replay it, gaining administrator access if an admin session is logged. The CVE is not in the CISA KEV catalog, and public PoC code exists. - Scanner behavior: probes
/wp-content/debug.log,/wp-content/uploads/wp-content/debug.log,/logs/wp-content/debug.log,/wordpress/wp-content/debug.logand the rotateddebug.log.1. It also uses URL-encoding evasion (debug%2elog) and cache-busting query strings. - Fingerprints: HTTP/1.0 with
Connection: close, two spoofed User-Agents shared across unrelated IPs, and X-Real-IP/X-Forwarded-For set to the scanner's own IP. Two header-casing variants suggest at least two tool builds. - Co-occurrence: CVE-2005-0869 (phpSysInfo, #9, 1,846 attacks) fires at near-identical per-IP counts, indicating one tool with a broad check library rather than chained exploits.
- Other trends: four Exchange-related CVEs are active (CVE-2021-26855 debuted at #4 with 3,163 attacks, alongside CVE-2022-41082 and CVE-2021-34523). CVE-2025-55182 grew by 1,526 to 3,086. CVE-2025-55184 fell from #7 to #12. Information Leakage events rose 77% to 1,149,567.
- Sources: the US is the top origin (7.73M events), followed by Germany, France and Singapore. China appeared as a new origin with 690,212 events after zero the prior month. Attribution is infrastructure-based only.
- Scanner IPs (top cluster): 5.189.184.50, 2.59.156.103, 144.126.159.74, 103.200.219.112, 195.26.240.180.
Remediation
- Update LiteSpeed Cache beyond 6.5.0.1 and disable debug logging in production; if logging is required, keep the log path non-web-accessible.
- Block external requests to debug.log paths, including nested, rotated and URL-encoded variants. Prefer path-based signatures over IP blocking, since source IPs rotate.
- Rotate WordPress secrets and force re-authentication if a vulnerable version ran with debug logging enabled; audit admin accounts for unexpected sessions or new administrators.
- Verify patch levels for on-premise Exchange (ProxyLogon/ProxyShell), prioritize patching PHP-CGI (CVE-2024-4577), and treat React SSR exposure to CVE-2025-55182 as urgent.
- Use ASN-level filtering rather than blanket geo-blocking of US/DE/FR/SG traffic.
- Mechanism: with WordPress debug logging enabled, LiteSpeed Cache (versions up to 6.5.0.1) writes session and cookie data to