Hispasec•July 22, 2026•🇪🇸Translated from Spanish

Critical wp2shell Vulnerability Chain Exploited in WordPress for Unauthenticated Remote Code Execution and Webshell Deployment

A critical vulnerability chain in WordPress Core, known as wp2shell, is being actively exploited to achieve unauthenticated remote code execution and install persistent webshells. The issue has been addressed in WordPress 7.0.2, 6.9.5, and 6.8.6, and site owners are strongly advised to apply updates without delay while checking exposed servers for signs of compromise.

Administrators running recent versions of WordPress Core currently face a direct threat. The wp2shell chain allows attackers to take full control of the server without any credentials and is already being used in real-world attacks to deploy webshells and malicious plugins. The risk primarily affects installations on the 7.0.x branch before 7.0.2 and the 6.9.x branch before 6.9.5, with a fixed release also available for the 6.8 branch at version 6.8.6.

Technical Details of the Exploit Chain

The core of the attack lies in the WordPress REST API, specifically its batch processing mechanism. Attackers combine two vulnerabilities, CVE-2026-63030 and CVE-2026-60137, to move from seemingly legitimate requests to full unauthenticated remote code execution. The first flaw involves a path confusion issue in the batch processing endpoint, while the second exploits an SQL injection in WP_Query tied to the author__not_in parameter. Together these issues allow escalation from manipulated queries to arbitrary code execution on the server.

Observed indicators align with automated attack campaigns. These include widespread scanning of WordPress instances, queries to the REST API to enumerate potential administrators, and collection of usernames and email addresses. In parallel, attackers attempt local file inclusion targeting wp-config.php to extract database credentials and authentication keys.

Persistence and Post-Exploitation Activity

Once access is gained, the primary goal is establishing persistence. Attackers have been observed creating PHP webshells in paths such as wp-content/cache using random filenames. These webshells return a fake 404 response unless the expected parameter is supplied. In some cases, intruders also create fraudulent administrator accounts or install plugins that facilitate remote control.

Recommended Mitigation Steps

The immediate priority is updating to WordPress 7.0.2, 6.9.5, or 6.8.6 depending on the installed branch and verifying that automatic security updates have been applied. After patching, administrators should review access and application logs for anomalous requests to the REST API and its batch endpoints, inspect installed plugins, and remove any recent unauthorized user accounts.

It is also recommended to search for newly created PHP files in unusual locations inside wp-content, audit users with elevated privileges, and delete any unauthorized accounts. If there are indications that wp-config.php was accessed, database credentials, authentication keys, and admin panel passwords must be rotated. In confirmed compromise scenarios, the response should include containment, clean reinstallation from a trusted backup, and full rotation of all secrets to eliminate persistence.

Related articles

Habr•Vulnerabilities & Exploits

F6 Investigates First In-the-Wild Exploitation of Critical CVE-2026-76466 in Cisco Expressway

Russian cybersecurity firm F6 has documented the first confirmed exploitation of the critical CVE-2026-76466 vulnerability (CVSS 9.8) affecting Cisco Expressway devices. Attackers targeted a Russian company and quickly adapted a public proof-of-concept exploit to gain root-level remote command execution on version X15.5.3. The flaw resides in the Erlang distribution authentication mechanism on TCP port 4372, allowing unauthenticated command execution via a hardcoded cookie. After initial access, the threat actors deployed over 100 custom Python scripts for network reconnaissance, lateral movement, and data collection, including tools that abused WinRM, SMB, LDAP, and SQL Server protocols. F6 observed modifications to the original PoC that enabled arbitrary command execution and result retrieval, along with auxiliary scripts for TCP relaying and repeated connection attempts. The incident highlights how quickly public exploits can be weaponized against perimeter devices that bridge external and internal networks.

Securitylab•Vulnerabilities & Exploits

NGINX2Root Vulnerabilities: Ten Critical Flaws Patched in NGINX Including Remote Code Execution via HTTP/2

On November 18 2026 NGINX developers addressed ten vulnerabilities with five grouped under the NGINX2Root research name by Theori's Xint team. The most severe CVE-2026-123007 enables unauthenticated remote code execution on servers with HTTP/2 enabled by exploiting memory corruption that originated in 2015. Researchers demonstrated full compromise including root escalation via a separate Linux SCTP kernel flaw and escape from Docker containers. Working exploits have been published by Rapid7 and others with specific requirements such as AVX-512 support and substantial traffic volumes. Patches are available in NGINX 1.30.7 1.31.9 and corresponding NGINX Plus releases while temporary mitigations include disabling HTTP/2 or HTTP/3. The issues affect standalone servers reverse proxies Kubernetes ingress controllers and embedded NGINX instances across distributions.

安全客•Vulnerabilities & Exploits

Linux Kernel CVE-2026-98432 Enables Remote Code Execution Across Nearly All Versions Since 4.4

China's NVDB issued a high-severity advisory on November 18 warning of a remote code execution flaw in the Linux Kernel that grants attackers full root privileges. The vulnerability affects Linux Kernel 4.4 and virtually every subsequent mainline release, impacting major distributions including Ubuntu, Debian, Red Hat, SUSE, Oracle, and Chinese variants such as Kylin, UnionTech, and Deepin. Because the flaw is remotely exploitable without prior authentication and leads directly to highest privileges, exposed public-facing systems face immediate risk. The advisory notably states that AI models can rapidly analyze patches, identify trigger conditions, and generate working exploit chains, shrinking the traditional window between disclosure and weaponization from days to hours. Official fixes have been published for multiple stable branches, yet administrators must still validate driver compatibility, container runtimes, and third-party modules before deploying kernel updates in production. The advisory also highlights incomplete vulnerability disclosures across PHP, Node.js, Apache, Chrome, GitLab, and MySQL, underscoring the need for precise asset inventories rather than reliance on vulnerability databases alone.

Habr•Vulnerabilities & Exploits

Wireshark 4.6.10 Released with Fixes for 39 Vulnerabilities and Multiple Protocol Dissectors

The open-source network protocol analyzer Wireshark has received its 4.6.10 update, addressing 14 bugs along with 39 security vulnerabilities discovered during testing. The release continues the 4.6 development branch that began in October 2025 and follows the long-standing stable line that started with version 1.0.0 in 2008. Patches cover a wide range of protocol dissectors including RTSE, NBAP, IEEE 1609.2, IrDA, Matter, IEEE 1905, OpenWire, USB-PTP, Exported PDU, ACN, PROFINET, SDP, MsgPack, NNTP, TLS, and SCTP. Additional corrections resolve infinite loops in the Kafka dissector and Tektronix K12xx file parser, heap disclosure issues, and a remote code execution flaw in LoRaWAN decryption tracked as ZDI-CAN-32851. The update also ships Npcap 1.89 for Windows installers and changes the default extcap directory on Unix-like systems to libexec for better multiarch compatibility.