AntiMalware•September 22, 2026•🇷🇺Translated from Russian

WordPress Click2Shell Flaw Chain Lets Attackers Achieve RCE via Single Admin Click

Researchers have identified a chain of vulnerabilities in WordPress core dubbed Click2Shell that permits remote code execution on the server without any attacker credentials. The attack succeeds when an authenticated administrator simply opens a maliciously prepared preview link.

The flaw stems from inconsistent handling of a single URL parameter used for theme previews. The theme directory API sanitizes the value and selects a legitimate theme, while the JavaScript running in the administrator’s browser inserts the original unsanitized string into a jQuery selector. This allows the prepared URL to force the WordPress interface to click the install button automatically.

No manual selection of “Install” or “Activate” is required from the administrator, and the installed theme remains inactive so the site continues to function normally from the outside. To achieve full remote code execution, the researchers combined the core issue with a second vulnerable component: the Mobile Repair Zone 2.5.4 theme available in the official directory.

During preview, WordPress loads the theme’s PHP code, after which an insecure AJAX handler permits downloading and executing an arbitrary plugin. The attacker can then read wp-config.php, steal database keys, modify files, create new administrator accounts, and inject scripts.

The attack is not fully automatic; it requires a logged-in administrator with the Administrator role to open the link. Authors and Editors lack the necessary privileges. Delivery can occur through targeted phishing or an existing XSS vulnerability.

WordPress resolved the issue in version 6.7.1 and released patches for all supported older branches. Because full technical details and proof-of-concept code are already public, immediate updating is strongly recommended. As a temporary safeguard, administrators can set the DISALLOW_FILE_MODS constant to prevent installation of themes and plugins, but applying the official patches remains the only complete fix.

Related articles

Securitylab•Vulnerabilities & Exploits

Java4Shell (CVE-2026-114938) Vulnerability Allows Remote Memory Corruption and Code Execution in OpenJDK

Researchers at Calif disclosed Java4Shell (CVE-2026-114938) on 17 November 2026, a critical flaw in the HotSpot JVM that enables memory corruption via a malicious Base64 payload. The issue affects multiple OpenJDK distributions including Oracle Java, Amazon Corretto, Eclipse Temurin and Azul Zulu when running on modern Intel Xeon and AMD EPYC processors supporting AVX-512 VBMI instructions. Rated 9.2 on CVSS 4.0, the vulnerability can lead to data theft and arbitrary code execution without authentication in several widely used products such as Keycloak, Jenkins and Atlassian Jira. Public exploit code and reconnaissance activity were observed within days, although no confirmed successful breaches have been reported yet. Patches are available for supported branches, while older intermediate versions require migration to maintained releases.

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.