Critical Unauthenticated File Upload Flaw in WooCommerce Wholesale Lead Capture Enables Active PHP Web Shell Attacks
Attackers are actively exploiting a critical vulnerability in the premium WooCommerce Wholesale Lead Capture plugin to compromise WordPress sites and gain full control of the underlying server.
The flaw, identified as CVE-2026-27540 and rated CVSS 9.8, permits unauthenticated file uploads. Attackers can plant a PHP web shell and execute arbitrary commands remotely. The issue impacts all installations running version 2.0.3.1 and earlier.
The technical vector centers on the publicly accessible AJAX endpoint wwlc_file_upload_handler. This handler validates file extensions against an allowlist that an attacker can override by manipulating the file_settings parameter, enabling PHP files to be accepted. Once uploaded, the shell can be executed directly from the browser to deploy additional payloads, steal credentials, or establish persistence.
Telemetry shows more than 100,000 exploitation attempts blocked since June 2026, with notable spikes between 4–17 June, on 1 July, and on 30 August. Multiple repeat IP addresses have generated tens of thousands of requests, consistent with automated scanning campaigns targeting vulnerable sites across the internet.
The developer published WooCommerce Wholesale Lead Capture 2.0.3.2 on 20 February 2026. Sites that cannot update immediately should disable or remove the plugin. Administrators must also scan wp-content/uploads for unexpected or recently created .php files and review logs for requests to /wp-admin/admin-ajax.php with the action wwlc_file_upload_handler.
Additional defensive measures include deploying WAF rules to block malicious uploads via admin-ajax.php and monitoring for repeated failed or successful requests from the same sources. In cases of confirmed intrusion, simply deleting a single file is insufficient; unknown administrator accounts should be removed, credentials rotated, and the site restored from a verified clean backup after hardening.
Related articles
Zero-Day Vulnerabilities: The Invisible Threats Lurking in Modern Software
Zero-Day vulnerabilities represent one of the most challenging problems in cybersecurity because developers have no time to prepare defenses before exploitation begins. These flaws exist in software components without the knowledge of vendors, leaving antivirus tools and existing security mechanisms unable to detect attacks. Researchers discover such issues through techniques including fuzzing, reverse engineering, and static analysis. High-profile examples such as Heartbleed in OpenSSL, EternalBlue in Windows SMB, and Log4Shell in the Log4j library illustrate how single errors can affect millions of systems worldwide. Bug Bounty programs now allow companies to harness independent researchers to find problems before criminals exploit them. Organizations can reduce risk through regular updates, least-privilege principles, multi-factor authentication, and layered defenses, though complete elimination of zero-day risk remains impossible.
11-Year-Old Linux Kernel Race Condition NoisyTCP (CVE-2026-99288) Enables Remote DoS on Nginx, Apache and SSH Servers
Security researcher Hyunwoo Kim disclosed NoisyTCP (CVE-2026-99288), an 11-year-old race condition in the Linux kernel networking stack that allows unauthenticated remote attackers to trigger kernel panics and crash servers. The flaw stems from concurrent access to the ehash table during TCP socket lookup, where one CPU context may dereference a freed request_sock or full socket while another reuses the memory via SYN cookies. Exploitation requires multiple RX queues or RPS enabled and succeeds reliably on virtualized environments within seconds to minutes. Affected systems include nearly all distributions running kernels from 4.4 onward until the fix landed in November 2026. Temporary mitigations involve disabling SYN cookies or restricting traffic to a single RX queue, though both reduce resilience or performance. The researcher published full technical details on GitHub after coordinated disclosure.
Check Point Gateways Hit by PHP2Shell Exploits Installing TSGA Backdoor via Chained CVEs
An unidentified threat actor has been actively exploiting known vulnerabilities in unpatched Check Point Security Gateways to deploy the TSGA backdoor. The campaign began on 30 October 2026 against Israeli organizations and expanded on 2 November to targets across multiple countries and industries. Initial access leveraged CVE-2026-109618 and CVE-2026-109619 in exposed Mobile Access portals, followed by local privilege escalation through the previously unknown CVE-2026-123039 in Gaia OS. Attackers then installed PHP web shells and the TSGA backdoor, which provides encrypted remote access, configuration theft, persistence mechanisms, and log tampering via the embedded TSProxy component. In the first wave, operators pivoted to VMware ESXi hosts and deployed the destructive wiper destroy_v6. While tooling overlaps with the China-linked Armory Castle group’s PhiliKit framework, the use of a wiper and references to the Israel-Palestine conflict leave attribution open to three scenarios.
Apache Shiro Authentication Bypass Vulnerability Disclosed, Fixed in August Update
A critical authentication bypass vulnerability has been identified in the Java security framework Apache Shiro under specific LDAP caching configurations. The flaw, tracked as CVE-2026-129349, affects versions prior to 3.0.0 and carries a CVSSv4.0 base score of 9.1, rated Critical. Once a valid user authenticates successfully, subsequent login attempts using the cache accept any password for that username, enabling impersonation attacks. The Apache Shiro development team disclosed the issue on November 14, 2026, noting that the vulnerability was already resolved in version 3.0.1 released in August 2026. Version 3.0.2 was made available on November 8, 2026, and users are urged to upgrade immediately to the latest release.