WordPress Exploitation Wave: Over 440,000 Attacks Target Critical Flaws in Elementor Pro and Super Forms

🛡️ Verified Threat IntelDigitalSpying Research Desk
📅 September 5, 2026⏱️ 5 min read

Published: September 5, 2026

Author: Security Research Team, DigitalSpying.com

Category: Web Application Security / CMS Vulnerabilities / Remote Code Execution

Executive Summary

A massive, highly coordinated exploitation campaign is currently sweeping across the WordPress ecosystem. According to urgent threat telemetry released by Wordfence and reported by The Hacker News and BleepingComputer, threat actors have launched over 440,000 automated exploit attempts in a span of just 72 hours, targeting critical remote code execution (RCE) vulnerabilities in two widely installed WordPress plugins: Elementor Pro and Super Forms.

The primary vulnerability under weaponization, tracked as CVE-2026-32475 in Elementor Pro, alongside an unauthenticated file-upload flaw in Super Forms, allows attackers to bypass standard input validation, upload malicious PHP web shells, and achieve complete server takeover without requiring administrative privileges. With millions of active websites relying on these tools for page building and lead generation, website administrators and hosting providers are urged to verify plugin patch levels immediately.

Deep-Dive Technical Analysis

1. Root Cause Analysis: Insecure AJAX Endpoint Handling & File Upload Bypasses

The exploitation campaign leverages distinct architectural flaws within the affected plugins' client-server communication channels:

* Elementor Pro (CVE-2026-32475 - Broken Access Control to Arbitrary File Upload): The vulnerability originates within an AJAX action handler responsible for processing dynamic component template uploads and form data. In affected versions, the handler fails to perform adequate capability checks (current_user_can()) and lacks robust nonce validation. An attacker can transmit a crafted multipart form request containing a serialized PHP payload disguised with image MIME headers (image/jpeg or image/png). Because the backend file-naming sanitizer fails to strip executable extensions (.php5, .phtml, or double extensions like .php.png), the payload is saved directly into the /wp-content/uploads/ directory with executable permissions.

* Super Forms (Unauthenticated Arbitrary File Upload): Super Forms incorporates an AJAX endpoint designed for file attachment submissions in public contact forms. Due to improper validation of user-defined destination directories and insufficient file extension whitelisting, attackers manipulate the upload destination path, allowing executable PHP scripts to be written outside temporary storage directly into public web directories.

2. Exploitation Lifecycle & Observed Attack Chains

Threat intelligence feeds indicate that the campaign is heavily automated and distributed across thousands of compromised IP addresses:

1. Mass Fingerprinting & Version Probing: Automated botnets scan WordPress targets by requesting standard plugin metadata endpoints (/wp-content/plugins/elementor-pro/readme.txt) to identify vulnerable versions.

2. Web Shell Delivery: Attackers issue POST requests to admin-ajax.php carrying lightweight, obfuscated PHP loaders (e.g., base64-encoded eval() or assert() stagers).

3. Database & Configuration Harvesting: Upon establishing a web shell, attackers execute commands to read wp-config.php, exfiltrating database credentials, authentication salts, and database host details.

4. Site Defacement & Malvertising Injection: Attackers inject malicious JavaScript redirects into active theme files (header.php and functions.php) to divert organic search traffic to scam sites, while creating hidden administrator accounts (wp_user tables) for long-term persistence.

Industry Impact & Broad Attack Surface

* Vast Attack Surface: Elementor Pro is one of the most widely adopted visual page builders in the world, powering millions of commercial, e-commerce, and corporate websites. Even a small fraction of unpatched sites represents hundreds of thousands of potential staging grounds for cybercriminals.

* Botnet Recruitment & SEO Poisoning: Compromised WordPress environments are frequently recruited into distributed denial-of-service (DDoS) botnets, used as spam relays, or weaponized for black-hat SEO poisoning, severely damaging brand reputation and search engine rankings.

* Shared Hosting Threat Vector: On shared web hosting platforms without proper user isolation (e.g., missing CloudLinux CageFS or open_basedir restrictions), a single compromised WordPress site can allow attackers to traverse directories and compromise neighboring customer accounts.

Actionable Recommendations & Defense Protocols

1. Update Plugins Immediately

* Upgrade Elementor Pro to the latest release (version 3.24.0 or higher) immediately via the WordPress Dashboard or WP-CLI (wp plugin update elementor-pro).

* Upgrade Super Forms to version 4.9.95 or higher immediately.

* If automatic updates are disabled, perform manual updates through your hosting cPanel or SFTP client.

2. Scan for Active Indicators of Compromise (IoCs)

* Inspect Upload Directories: Audit /wp-content/uploads/ and plugin asset folders for newly created .php, .phtml, or .ico files containing executable PHP code.

* Audit Administrator Accounts: Review the WordPress Users table for unauthorized administrator accounts created within the last 7 days.

* Examine Theme Integrity: Verify core theme files (functions.php, index.php, header.php) against known-clean repository backups to detect injected JavaScript redirect loops.

3. Implement Strict Web Application Firewall (WAF) Rules

* Deploy WAF rules that block direct execution of PHP files located within /wp-content/uploads/.

* For Apache/LiteSpeed web servers, place a .htaccess file inside /wp-content/uploads/ with:

deny from all

* For NGINX servers, ensure location blocks disallow PHP execution in upload paths:

location ~* /wp-content/uploads/.*\.php$ {

deny all;

}

4. Enforce Principle of Least Privilege

Ensure file system permissions restrict web server write access to only necessary directories. System files and core plugins should be owned by a non-web user with read-only permissions for the PHP runtime (chmod 755 for directories, chmod 644 for files).

Stay informed on web application vulnerabilities, CMS security alerts, and threat analysis at DigitalSpying.com.

Classification:Cyber Security IntelligenceZero-Day AnalysisDefensive Engineering
🛡️

About the DigitalSpying Research Desk

The DigitalSpying Threat Intelligence Desk is composed of seasoned security researchers, reverse engineers, and blue team architects. Our mission is to publish reproducible, peer-audited threat analyses, hardware security evaluations, and defensive countermeasures.