Last updated: November 2, 2026 at 1:20 PM UTC
All 957 Vulnerability 399 Breach 144 Threat 407 Defense 7
Tag: wordpress (34 articles)Clear

WordPress Core upgrade race condition draws nearly 63,000 code execution attempts in 24 hours

Wordfence blocked 62,969 attacks in 24 hours against a WordPress Core remote code execution flaw, rated 8.1 and tracked under GitHub advisory GHSA-4w3m-c66w-69mg with no CVE assigned. The flaw stems from predictable, web-accessible staging paths used during full-package core upgrades: new files, including the WordPress installer, are unpacked into a predictable wp-content/upgrade directory, and an unauthenticated attacker who requests the installer at the right moment can reach PHP code execution by winning a narrow race condition. It affects WordPress 4.7 through 7.1.3 and is fixed in 7.1.4, released October 28. Attackers are polling paths such as setup-config.php.

Check
Update WordPress Core to 7.1.4 now, and watch web logs for requests to wp-content/upgrade paths such as setup-config.php during and after upgrades.
Affected
WordPress sites on 4.7 through 7.1.3 expose a predictable upgrade staging path that an unauthenticated attacker can race to reach PHP code execution.
Fix
Apply WordPress 7.1.4, block external requests to wp-content/upgrade, and review sites for web shells or unexpected admin changes after the attack window.

Attackers abuse stolen UpdraftCentral keys to install backdoor plugins on connected WordPress sites

TeamUpdraft disclosed that attackers breached its website over the October 17 weekend and reached its customer database, obtaining names, emails, hashed passwords, 2FA settings, and the UpdraftCentral connection keys that let them push backdoor plugins to connected WordPress sites. UpdraftPlus, a backup plugin with over four million installs, ships an UpdraftCentral client in every copy. Patchstack saw signed plugin.upload_plugin commands over an 18-hour window and 99 backdoor plugin names, and one backdoor creates a persistent data-ops43 editor account that survives plugin removal. Fixes are in UpdraftPlus 1.26.13 and 2.26.13, which disconnect pre-incident UpdraftCentral connections. Site owners should rotate keys and hunt for rogue accounts.

Check
Update UpdraftPlus to 1.26.13 or 2.26.13, delete the UpdraftCentral connection key, and check WordPress sites for unknown admin or editor accounts and plugins.
Affected
WordPress sites connected to cloud UpdraftCentral could receive attacker-pushed backdoor plugins and a persistent data-ops43 account that survives plugin removal and normal login unless 2FA blocks it.
Fix
Apply the fixed UpdraftPlus release, rotate UpdraftCentral and storage keys, remove rogue accounts and plugins including must-use plugins, and restore from a pre-October-17 backup if needed.

Attackers exploit unauthenticated Bricksforge WordPress plugin flaw allowing arbitrary PHP upload and remote code execution

Patchstack detected active exploitation of CVE-2026-85097, a flaw rated 10.0 in the Bricksforge WordPress plugin, beginning October 7. The plugin does not validate the url field inside its temporaryFileUploads parameter, letting an unauthenticated attacker upload and execute arbitrary PHP code on vulnerable sites. Exploitation came from 63 unique source IPs, with six responsible for roughly 46 percent of requests. Versions up to and including 3.1.8.9 are affected; the vendor released a fix in 3.1.8.10, and the current release is 4.0.1. Wordfence published an advisory. Site operators should update immediately and check for unexpected PHP files and administrative changes.

Check
Update the Bricksforge plugin to at least 3.1.8.10, ideally 4.0.1, on all WordPress sites, then check for unexpected PHP files and new administrator accounts.
Affected
WordPress sites running Bricksforge up to 3.1.8.9 let an unauthenticated attacker upload and execute arbitrary PHP code, and exploitation has been underway since October 7.
Fix
Upgrade Bricksforge immediately, scan for web shells and unauthorized files, remove rogue admin accounts, rotate credentials and keys, and restrict access to the WordPress admin interface.

Attackers exploit Ninja Forms WordPress plugin stored cross-site scripting flaw to plant site backdoors

Patchstack identified a campaign on October 4 exploiting CVE-2026-94504, a high-severity stored cross-site scripting flaw in the Ninja Forms WordPress plugin, which is installed on more than 500,000 sites. Attackers plant malicious JavaScript in form submissions, and when a logged-in administrator loads the content, the script runs under the authenticated WordPress session. The payload installs a backdoor plugin and creates several hidden access paths: a visible administrator account, a concealed account kept out of the user list, a secret login URL, and unauthenticated file manager access. Versions 3.15.3 and older are affected, with a fix in 3.15.4.

Check
Update the Ninja Forms plugin to 3.15.4 or later on all WordPress sites, then check for unknown administrator accounts, rogue plugins, and hidden login paths.
Affected
WordPress sites running Ninja Forms 3.15.3 or older let attackers store malicious JavaScript that runs in an administrator's session to install backdoors and hidden admin accounts.
Fix
Upgrade Ninja Forms, remove unauthorized admin accounts and backdoor plugins, rotate credentials and keys, and audit for secret login URLs and file manager access.

WordPress SC backdoor rebuilds itself from files database and shared memory after cleanup

Sucuri detailed a WordPress compromise using a backdoor it codenamed SC, after SC_ markers in the injected content, which it describes as a self-healing mesh. The payload lives in at least eight places at once, spread across files, the database, and a shared-memory segment, and every location can rebuild all the others. Cleaning every file on disk lets the next page load restore the whole set from the database or shared memory, so there is no single point to remove. The malware carries no readable function names, using a substitution cipher to unscramble its code, and a .user.ini auto_prepend_file runs a loader before every PHP request.

Check
Treat infected WordPress sites as needing coordinated full cleanup across files, database, and runtime, and rebuild from a known-good backup where feasible.
Affected
WordPress sites hit by the SC backdoor cannot be cleaned piecemeal, since files, database entries, and shared memory each regenerate the removed components.
Fix
Take the site offline during cleanup, purge all eight component types together, rotate credentials and keys, restore from clean backups, and harden PHP auto_prepend_file.

Elementor WordPress plugin flaw lets one link create a rogue administrator account

Patchstack detailed a high-severity cross-site request forgery flaw, rated 8.8 and not yet assigned a CVE, in the Elementor Website Builder WordPress plugin, which is active on over ten million sites. It affects only versions 4.3.0 and 4.3.1, installed on more than two million sites, and is fixed in 4.3.2. One link opened by a logged-in WordPress user makes that user perform any REST API action their account permits, so an administrator clicking it creates a second administrator account for the attacker on a stock install. The attack needs no JavaScript, submitted form, or attacker-controlled page; the link can be a plain anchor tag in an email, chat, or comment.

Check
Update the Elementor plugin to 4.3.2 across all WordPress sites, then audit administrator accounts for unexpected additions created via the flaw.
Affected
Sites running Elementor 4.3.0 or 4.3.1 let an unauthenticated attacker trick a logged-in admin into creating a rogue administrator account by clicking a link.
Fix
Apply Elementor 4.3.2, remove unrecognized admin accounts, and warn administrators against opening untrusted links while signed in to WordPress.

Attackers exploit unauthenticated WordPress code execution flaw within hours of its disclosure

Threat actors began exploiting a critical WordPress flaw, CVE-2026-87902, rated 9.2, within hours of its public disclosure. The bug lets an unauthenticated attacker make get_page_template() include a chosen readable local .php file outside the active theme directories, which can lead to remote code execution when server and theme preconditions are met. Exploitation requires the active child or parent theme to contain a top-level directory whose name starts with page-, and a readable local .php target such as pearcmd.php. Previdian reported honeypot exploitation attempts from a New Jersey IP that include /usr/local/lib/php/pearcmd.php, write a file to /tmp, then pull a PHP upload script from GitHub to plant a web shell.

Check
Update WordPress to the patched release now, then check whether active themes contain page- prefixed directories and review web logs for pearcmd.php requests.
Affected
WordPress sites meeting the theme and server preconditions let an unauthenticated attacker chain local file inclusion into remote code execution, already seen in the wild.
Fix
Apply the WordPress patch, harden PHP to disable pearcmd.php inclusion, and block the observed exploit indicators at the web tier.

WordPress flaw forces theme installs and can chain to server code execution

WordPress shipped 7.1.1 on September 17 to fix a flaw that pwn.ai calls Click2Shell, where a crafted link opened by a logged-in administrator installs a theme from the official directory with no click. Two parts of WordPress read the link differently, so attacker-added characters steer the admin browser into clicking Install, and the logged-in session supplies the permission and security token. Alone it only installs a real, switched-off theme, but the researchers chained it with a second flaw in the Mobile Repair Zone theme, whose handler fetched and ran remote code during a Customizer preview, reaching server code execution. No in-the-wild abuse is reported.

Check
Update all WordPress sites to 7.1.1 immediately, then audit installed themes for unexpected additions and remove any that administrators did not intend.
Affected
Sites where an administrator opens a crafted link can silently install an attacker-chosen theme, which can chain with a vulnerable theme to code execution.
Fix
Apply 7.1.1, remove unused themes, and warn administrators against opening untrusted links while authenticated to the WordPress dashboard.

WordPress backup plugin flaw lets attackers hijack sites through a poisoned import

A flaw in All-in-One WP Migration and Backup, a WordPress plugin installed on millions of sites, can let an unauthenticated attacker take over a site. Tracked as CVE-2026-19949, it is a second-order SQL injection caused by incorrect handling of escaped characters when the plugin rewrites database content during a restore. An attacker plants crafted data through WordPress trackbacks, which triggers when an administrator exports and imports the site, both routine plugin operations. The injection can leak the plugin's secret import key through a public comment, letting the attacker import a malicious backup archive containing executable code and seize full control. ServMask fixed it in version 7.110, but many sites remain unpatched.

Check
Update All-in-One WP Migration and Backup to 7.110 or later across all WordPress sites, and review sites for suspicious trackback comments, unexpected admin accounts, and unfamiliar files.
Affected
WordPress sites running All-in-One WP Migration and Backup through 7.109 (CVE-2026-19949); an unauthenticated attacker can plant SQL injection that leaks the plugin's secret key, enabling a malicious archive import and site takeover.
Fix
Patch the plugin, scan for web shells and unexpected files, audit administrator accounts, rotate WordPress secrets, disable trackbacks if not needed, and put a web application firewall in front of the site.

Critical WordPress plugin and theme flaws let unauthenticated attackers seize sites

Researchers at Wordfence and Patchstack disclosed a cluster of critical WordPress vulnerabilities, most scored 9.8, that let unauthenticated attackers take over sites or run code. In the WPMU DEV Dashboard plugin, CVE-2026-76581 is a single-sign-on authentication bypass that can hand an attacker an administrator session. The Avada theme's CVE-2026-18431 allows arbitrary file writes that lead to remote code execution. In the Pods plugin, CVE-2026-19598 lets an attacker escalate to administrator or overwrite any user's password, while TranslatePress's CVE-2026-19632 exposes the raw administrator password-reset link. Each independently enables full site compromise, and a separate GiveWP flaw in the same batch was covered earlier.

Check
Inventory your WordPress sites for the WPMU DEV Dashboard, Avada, Pods, and TranslatePress components, and update each to its patched version now, prioritizing internet-facing and multi-author sites.
Affected
Sites running vulnerable versions of WPMU DEV Dashboard, Avada, Pods, or TranslatePress (CVE-2026-76581, CVE-2026-18431, CVE-2026-19598, CVE-2026-19632); unauthenticated attackers can gain admin access, reset passwords, or execute code.
Fix
Patch every affected plugin and theme, audit for unexpected admin accounts, changed passwords, and new PHP files, front sites with a web application firewall, and rotate credentials on any exposed site.