Urgent.News

What's breaking now, across thousands of outlets.

Tech

Click2Shell Exposure: What 7.9 Million WordPress Assets Do and Do Not Tell You

Click2Shell Exposure: What 7.9 Million WordPress Assets Do and Do Not Tell You The Click2Shell disclosure on September 21, 2026 described an unauthenticated RCE chain in WordPress Core: a crafted link makes a logged-in administrator's browser install a catalog theme automatically, then the theme's unprotected AJAX handler pulls attacker PHP from a remote package and executes it. WordPress shipped…

On September 21, 2026, a security disclosure revealed a critical vulnerability in WordPress Core known as Click2Shell. The exploit involves a crafted link that, when visited by an administrator, installs a malicious theme automatically. This theme's unprotected AJAX handler then pulls and executes attacker PHP from a remote package. The vulnerability was patched in WordPress version 7.1.1.

According to ZoomEye, an internet search engine for Internet of Things (IoT) devices, there were 7,945,496 matching WordPress assets globally as of September 22, 2026. However, this figure is misleading. It represents indexed product assets, not confirmed vulnerable hosts. The chain has an authentication-shaped gate, requiring a logged-in administrator to visit an attacker-chosen URL before any code runs. This means that even if a WordPress instance is indexed, it does not necessarily mean it is vulnerable.

The exposure surface consists of two layers: the Core layer, which affects all versions before 7.1.1, and the Theme layer, which involves unprotected AJAX endpoints in specific themes. Even if the core is patched, a vulnerable theme can still pose a risk if an attacker can get that theme loaded during a Customizer preview. Therefore, a single product fingerprint cannot represent the entire exposure surface. Researchers found no in-the-wild exploitation, suggesting that the vulnerability has not been actively targeted yet.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

The QA Script That Checks 8,556 PDF Links (and What It Caught)

A link you never click is a bug your customer finds I generated an 871-page hyperlinked PDF planner with Python — 8,556 internal link annotations across 730 daily pages, 105 weekly spreads, 24 monthly…

  • QA script verifies 871-page hyperlinked PDF planner for broken links
  • Script checks every link annotation for correct destination page
  • Script caught bugs during development, prevented release issues

More from Sunday 27 September →