Critical wp2shell Vulnerabilities Lead to Exploitations

In recent developments, hackers have been exploiting critical vulnerabilities in the 'wp2shell' suite affecting WordPress Core, specifically CVE-2026-63030 and CVE-2026-60137. These exploits are enabling attackers to deploy persistent webshells and install malicious plugins on compromised servers.

The vulnerabilities take advantage of the batch-processing feature in the WordPress REST API, which allows remote attackers to execute code on vulnerable installations without needing authentication.

Although detailed technical information has not been fully disclosed, proof-of-concept exploits began circulating over the weekend after SearchLight Cyber revealed the wp2shell security issue.

Following the discovery, active exploitation was confirmed shortly after WordPress issued patches in versions 7.0.2, 6.9.5, and 6.8.6, which enforced automatic security updates for supported installations.

Cloud security firm Wiz has reported technical insights on the wp2shell exploits, detailing several activities undertaken by threat actors. These include:

• Mass-scanning for vulnerable WordPress installations, primarily for security scanning purposes.
• Abuse of the WordPress plugin upload feature to install malicious add-ons.
• Installation of PHP webshells, which can range from simple backdoors to complex, obfuscated shells masquerading as plugins (e.g., CMSmap).
• Querying the WordPress REST API to gather administrator usernames and email addresses.
• Attempting local file inclusion by targeting wp-config through admin-ajax.php to extract database credentials and authentication keys.
• Deploying malicious plugins that expose a REST API endpoint for remote command execution.
• Gaining unauthorized access to WordPress administration panels.

Wiz has noted that while there has been no evidence of lateral movement or data exfiltration, they are actively monitoring the ongoing threat activities.

Additionally, a report from Johannes B. Ullrich, Dean of Research at the SANS Technology Institute, highlights two-stage attacks. These begin with probing for SQL injection to confirm vulnerabilities before delivering a PHP webshell to the server.

The compromised webshell often appears in the /wp-content/cache/ directory, and accessing the page may return a false 404 error.

Ullrich also notes that some attacks involve the creation of rogue administrator accounts. He recommends checking the /cache/ directory for any unfamiliar entries and inspecting for newly created users.

The WordPress security firm Defiant has reported that the first signs of wp2shell exploitation were observed at 23:29 UTC on July 17, followed by a clear SQL injection attempt just 13 minutes later.

For administrators of WordPress sites, it is crucial to update to the latest patched versions immediately. Additionally, reviewing logs for wp2shell-related requests, inspecting installed plugins, and checking for unauthorized PHP files or new admin accounts are highly recommended.

Researcher Yutaka Sejiyama from Macnica has developed a live dashboard to track the patch rate, reporting an 81.6% patch rate from a sample of 124,580 evaluated websites.

Moreover, SearchLight Cyber researcher Adam Kues published a follow-up report detailing the discovery process of wp2shell and the development of an exploit chain, which involved utilizing AI tools.

As a closing note, it is vital for security teams to rigorously test every layer of their systems before attackers can exploit vulnerabilities. According to recent findings, security teams log only 54% of successful attacks while alerting on merely 14%, leaving a significant number of threats undetected.

Technology teams are watching critical wp2shell vulnerabilities lead to exploitations closely because changes in this space often arrive faster than internal policies can adapt.

For product and engineering leaders, the practical question is how this could reshape roadmaps, vendor choices, and security reviews over the next few quarters.

Organizations that document lessons early tend to respond more calmly when similar patterns appear again.

In many companies, the first impact shows up in planning meetings: teams reassess priorities, revisit risk registers, and check whether existing tooling still fits.

Smaller businesses feel these shifts too. A single platform change or market move can affect customer trust, delivery timelines, and hiring plans.

The most resilient teams treat stories like this as input for quarterly reviews rather than one-day headlines.

If your business depends on modern software, ERP, VoIP, or customer-facing apps, staying informed helps you separate noise from decisions that require action.

Looking ahead, disciplined follow-through matters: assign owners, set review dates, and measure whether your response improved outcomes.

Security and compliance stakeholders should ask whether current controls still match the pace of change described in this update.

Operations leaders can reduce friction by translating the headline into a short internal brief with clear next steps for each department.

Customer support teams may see early signals through tickets, outages, or policy questions long before leadership reviews are scheduled.

Finance and procurement groups should note whether licensing, vendor risk, or implementation costs need revisiting after this development.

Training programs benefit from timely updates so staff understand what changed, what did not change, and what requires escalation.

Architecture reviews are a practical place to test assumptions, especially when new tools, platforms, or threats enter the conversation.

Utilizing breach and attack simulation can effectively test SIEM and EDR rules, ensuring that potential threats are not overlooked.