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
Ghost Assets in Vulnerability Management: How Identification, Merging and Asset History Eliminate Anomalies in MaxPatrol VM
Positive Technologies experts explain how infrastructure changes create duplicate, merged and phantom assets that distort vulnerability management. The article details three core mechanisms inside MaxPatrol VM: unique asset identification across scan sources, non-destructive merging of new and existing data, and full lifecycle history with configurable aging policies. It describes how the system distinguishes assets using prioritized keys such as system ID, FQDN, MAC address and VM ID, then applies recursive merging rules that respect multiple data sources. Policies allow teams to set freshness and obsolescence thresholds, automatically hiding assets after 90 days while preserving historical snapshots for PDQL queries. The piece also covers practical cloning and partial-scan scenarios that can produce misleading duplicates or lingering collections.
GreyNoise Detects Active Exploitation Attempts of CVE-2021-36260 Against Hikvision Cameras
GreyNoise recorded exploitation attempts targeting CVE-2021-36260 in Hikvision cameras and recorders between September 21 and October 1. The vulnerability carries a CVSS score of 9.8 and allows unauthenticated remote command execution through insufficient input validation in the embedded web server. Attack traffic originated from four IP addresses, three routed through a commercial VPN in Lithuania and one from a Ukrainian residential network, with all targets located in Ukraine. Attackers leveraged a publicly available Nuclei template to probe devices, though GreyNoise confirmed only scanning activity and not successful compromises. The five-year-old flaw remains actively scanned despite an available firmware patch from Hikvision and a CISA advisory recommending immediate updates. Password changes provide no protection because the attack requires no authentication. Defenders are advised to apply firmware updates, remove devices from public internet exposure, and segment video surveillance networks from critical infrastructure.
Splunk Enterprise Discloses 46 Vulnerabilities Including Critical Patroni Authentication Flaw
Splunk has published three security advisories detailing a total of 46 vulnerabilities affecting Splunk Enterprise and related components. Three of the issues were rated critical, with CVE-2026-76268 receiving a CVSS v3.1 base score of 9.8. The flaw resides in the Patroni REST API used for PostgreSQL cluster management within search head clusters, allowing unauthenticated remote attackers to execute arbitrary operating system commands. Another high-severity issue, CVE-2026-76266, enables local privilege escalation to root on Linux systems during package updates. The remaining vulnerabilities cover product code, internally identified problems, and third-party packages. Organizations are urged to apply the available patches promptly.
Smart Fish Tank Power Strip Server Breached, Killing Aquarium Fish During National Day Holiday
During China's National Day holiday, the cloud servers of Woda Technology's smart power strips for fish tanks were compromised by malicious hackers, causing widespread remote disconnections and power outages for user devices. The attack left heating rods, oxygen pumps, and circulation systems offline for hours, resulting in the deaths of koi, arowana, and other ornamental fish that users had maintained for years. Woda issued a public notice confirming the intrusion was not a product defect or user error but a deliberate network attack, and the company has since upgraded firewalls, added multi-layer cloud protections, deployed backup servers, and improved local offline logic to prevent future failures. The incident highlights a critical IoT design flaw where devices rely entirely on vendor cloud platforms for control, allowing attackers who breach the server to remotely manage household appliances at scale. Security experts note that the same architecture is used across smart speakers, locks, cameras, and other consumer devices, creating a broad attack surface with minimal updates or segmentation. Woda has reported the case to authorities and preserved logs for forensic investigation.