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

Critical GiveWP WordPress flaw lets unauthenticated attackers run server commands

A critical flaw in GiveWP, a WordPress donation and fundraising plugin installed on more than 100,000 sites, lets an unauthenticated attacker run commands on the hosting server. Tracked as CVE-2026-82222, it chains three weaknesses: an unsafe PHP deserialization helper, a donation flow that stores attacker-controlled serialized objects, and a gadget chain in bundled libraries that turns that into system command execution. Although exploitation normally needs an account, an exposed registration action lets an attacker create one even when registration is disabled, making it effectively unauthenticated. It affects versions up to 4.16.7.1 and is fixed in 4.16.7.2, which blocks serialized data during donation processing.

Check
Update the GiveWP plugin to 4.16.7.2 across all WordPress sites now, and check for unexpected accounts, files, or processes on servers running the donation plugin.
Affected
WordPress sites running GiveWP up to 4.16.7.1 (CVE-2026-82222); an attacker can chain PHP object injection into system command execution, and a registration bypass makes exploitation effectively unauthenticated even with signups disabled.
Fix
Patch the plugin, put a web application firewall in front of the site, scan for web shells and unauthorized files, and review hosting accounts and logs on donation-enabled sites.

Attackers chain two miniOrange WordPress SSO flaws to forge admin logins

Attackers are exploiting two critical authentication-bypass flaws in the miniOrange SAML 2.0 Single Sign On plugin for WordPress, chaining them to forge login responses and sign in as an administrator. The first flaw, CVE-2026-61979, lets the plugin accept an attacker-chosen signature algorithm, so the identity provider's public key can be abused as a shared secret to forge a valid signature; the second, CVE-2026-15981, makes the plugin treat a signature-verification error as success. Both were fixed in July, but the vendor only alerted free-edition users, leaving paid editions unpatched. Security firm Patchstack traced an attack in mid-August where the two were chained to steal an administrator session cookie.

Check
Update the miniOrange SAML Single Sign On plugin on all WordPress sites, including paid editions that were not alerted, and audit for unexpected administrator accounts and sessions.
Affected
WordPress sites using the miniOrange SAML 2.0 Single Sign On plugin (CVE-2026-61979, CVE-2026-15981); chaining the two lets an unauthenticated attacker forge a SAML response and obtain an administrator session.
Fix
Patch or remove the plugin, rotate WordPress salts and admin passwords to invalidate stolen sessions, check for rogue admins, and put a web application firewall in front of login endpoints.

Critical Elementor Pro flaw lets unauthenticated visitors upload PHP and run code

Researchers disclosed a critical flaw in Elementor Pro, the widely used WordPress page builder, that lets an unauthenticated visitor upload a PHP file through a public form and run code on the server. Tracked as CVE-2026-32475 and scored 9.0, it is a desynchronization bug in the Forms module's file-upload field: the code that validates an upload and the code that saves it disagree about how to handle an empty file entry. By sending a crafted upload with an empty first part followed by a PHP payload, an attacker slips the file past validation into a public directory. It affects versions up to 4.2.1 and is fixed in 4.2.2.

Check
Update Elementor Pro to 4.2.2 across all WordPress sites, and because updating does not remove files already uploaded, inspect the Elementor forms upload directory for unexpected PHP files.
Affected
WordPress sites running Elementor Pro up to 4.2.1 with a published form containing a file-upload field (CVE-2026-32475); an unauthenticated visitor can upload a PHP file and execute code as the web server.
Fix
Patch to 4.2.2, scan for web shells and unexpected files in upload directories, put a web application firewall in front of the site, and restrict public upload forms until confirmed clean.

Unauthenticated Forminator flaw lets attackers upload PHP and take over WordPress sites

A critical flaw in Forminator Forms, a WordPress plugin with more than 600,000 installations, lets unauthenticated attackers upload executable PHP files and take over a site. Tracked as CVE-2026-15748 and scored 9.8, the bug chains weaknesses in the plugin's upload handling: an attacker smuggles a forged record through a Select field that declares itself a file upload, then slips a PHP file past a blocklist that only checks exact extensions. Exploitation requires a form with both a file upload field and a select field, and it affects all versions up to 1.56.1. Because it needs no authentication, automated scanners can hunt for vulnerable sites at scale.

Check
Update the Forminator plugin to a version newer than 1.56.1 across all WordPress sites, and check for unexpected PHP files in upload directories and unfamiliar administrator activity.
Affected
WordPress sites running Forminator 1.56.1 or earlier with a form containing both a file upload and a select field (CVE-2026-15748); an unauthenticated attacker can upload PHP and fully compromise the site.
Fix
Patch the plugin, put a web application firewall in front of the site, scan for web shells and unauthorized files, and remove or reconfigure vulnerable forms until the update is applied.

Poisoned banner feed turns BdThemes WordPress plugins into rogue-admin factories

Researchers at Wordfence found that attackers compromised the upstream infrastructure of BdThemes, a popular WordPress plugin vendor, and poisoned a remote JSON feed that its plugins fetch to show promotional banners in the admin dashboard. Because the malicious code lives in that feed rather than in the plugin source, no plugin update was needed and nothing changed on disk. The injected script runs in every logged-in administrator's browser, creates hidden rogue admin accounts through the site's own interface, and installs a fake plugin containing a web shell for persistence. Seven plugins including Element Pack and Prime Slider were affected, and the flaw sat unnoticed for about five months.

Check
If you run BdThemes plugins such as Element Pack or Prime Slider, check for unexpected administrator accounts and unfamiliar plugins, and look for a web shell file named emer-run dot php.
Affected
WordPress sites running affected BdThemes plugins; a poisoned vendor feed ran code in administrators' browsers to create hidden admin accounts and install a web shell, without any plugin update or on-disk change.
Fix
Update the plugins once cleaned versions ship, remove rogue admins and web shells, rotate administrator credentials, and treat remote content that plugins load into the dashboard as an attack surface to monitor.

WordPress pre-auth login XSS can chain to full server takeover

WordPress patched a pre-authentication reflected cross-site scripting flaw in the login screen that researchers showed can chain into PHP code execution and full server takeover, naming the chain XSS2Shell. Tracked as CVE-2026-64638 and scored 8.9, the cross-site scripting bug affects all WordPress versions and needs no login to trigger. On its own it runs script in a visitor's browser, but when a logged-in administrator is lured to an attacker-controlled page, the chain can reach code execution on the server. Because WordPress runs a large share of the web, a flaw affecting every version and needing no authentication has broad reach.

Check
Update WordPress to the patched release across every site, including forgotten and staging installs, and put a web application firewall in front of internet-facing sites.
Affected
All WordPress sites on versions before the fix (CVE-2026-64638); an unauthenticated attacker can run script in the login page, and luring an administrator to a crafted page can chain to code execution.
Fix
Apply the WordPress update, confirm automatic updates ran, use a web application firewall, and remind administrators to avoid unexpected links, since the chain to code execution runs through an admin's browser.

Public exploits released for WordPress core flaws that give anonymous code execution

Public exploit code is now available for wp2shell, a pair of WordPress core flaws that chain into pre-authentication remote code execution against a stock site with no plugins installed. CVE-2026-63030 is a route confusion bug in the REST API batch endpoint, which has shipped enabled by default since 2020, and CVE-2026-60137 is a SQL injection in the author parameter handling of WP_Query. Chained, an anonymous HTTP request can run code on the server. The chain affects WordPress 6.9.0 through 6.9.4 and 7.0.0 through 7.0.1, fixed in 6.9.5 and 7.0.2, and WordPress enabled forced automatic updates given the severity.

Check
Confirm every WordPress site you run, including forgotten and staging instances, is on 6.9.5 or 7.0.2 or later, then check logs and web directories for web shells.
Affected
Any site on WordPress 6.9.0 to 6.9.4 or 7.0.0 to 7.0.1 (CVE-2026-63030, CVE-2026-60137); no plugins, login, or user interaction are needed, and working exploits are public.
Fix
Update to WordPress 6.9.5 or 7.0.2, confirm auto-updates applied, put a web application firewall in front of exposed sites, and treat unpatched internet-facing installs as potentially compromised.

Australia warns of a global campaign hitting websites through known CMS flaws

Australia's Cyber Security Centre has warned of a large-scale global campaign in which attackers scan websites and exploit known vulnerabilities in content management systems and their plugins to plant web shells. The affected software spans WordPress, Joomla, Craft CMS, and others, with the flaws typically allowing unauthenticated file upload, remote code execution, or server-side request forgery. Once a web shell is installed, attackers can take a site offline, deface it, steal data stored on the server, or pivot deeper into the network. Many small and medium-sized businesses have already been hit, and the agency notes the campaign may be accelerated by AI, which helps attackers scale exploitation of newly disclosed flaws.

Check
Inventory your public websites and their CMS platforms, themes, and plugins, apply outstanding security updates, remove unused components, and review access and network logs and existing accounts for signs of compromise.
Affected
Organizations running internet-facing CMS platforms like WordPress, Joomla, or Craft CMS with unpatched plugins; attackers automatically exploit known flaws to plant web shells, disproportionately hitting small and medium-sized businesses.
Fix
Patch CMS software and plugins promptly, enable automatic updates where possible, make web directories read-only where feasible, restrict access to sensitive directories, and restore from a known-clean backup if compromise is found.

Exposed server reveals crew that backdoored thousands of WordPress sites for resale

A cybercrime group left its own server exposed on the internet for weeks, revealing a mass website-hacking operation that researchers at SOCRadar now track as WP-SHELLSTORM. The crew breaks into sites at scale, plants hidden backdoors, and resells the access to other criminals. Rather than using zero-days, it automated attacks against 27 known vulnerabilities in outdated WordPress and Joomla plugins; a single flaw in the Breeze caching plugin accounted for over 17,000 backdoored sites. Target lists named more than 1.4 million domains, with roughly 25,000 confirmed compromised. The same server also revealed an earlier campaign that stole cloud credentials and database passwords from exposed configuration servers.

Check
Update WordPress and Joomla plugins, especially the Breeze caching plugin and Joomla's JCE editor, and hunt for webshells with suspicious names and fake kernel-worker processes that indicate a backdoor.
Affected
Organizations running WordPress or Joomla sites with outdated, vulnerable plugins; the crew automatically exploits known flaws to plant backdoors, then sells that access, making even low-profile sites worthwhile footholds.
Fix
Keep plugins patched on a regular cadence, put a web application firewall in front of anything you cannot patch immediately, scan for known webshell indicators, and rotate credentials on exposed configuration servers.

Hackers mass-exploit Gravity SMTP WordPress flaw to steal email API keys

Attackers are mass-exploiting a flaw in Gravity SMTP, a WordPress email plugin installed on about 100,000 sites, to harvest credentials without any login. The bug (CVE-2026-4020) leaves a REST API endpoint with a permission check that always passes, so a single unauthenticated request returns a 365 KB system report containing API keys, secrets, and OAuth tokens for connected email services like Amazon SES, Mailjet, and Zoho, plus detailed software-stack information. Wordfence has blocked more than 17 million attempts, with activity spiking around June 6 and 7. A patch shipped in version 2.1.5, but updating does not revoke keys attackers may have already grabbed.

Check
Identify WordPress sites running Gravity SMTP at version 2.1.4 or earlier, and review web server access logs for requests to the /wp-json/gravitysmtp/v1/tests/mock-data endpoint, which indicate attempted or successful data exposure.
Affected
WordPress sites running Gravity SMTP through 2.1.4 with email integrations configured (CVE-2026-4020); exposed API keys and OAuth tokens let attackers abuse connected email services and map the site for follow-on attacks.
Fix
Update Gravity SMTP to 2.1.5 or later, then assume compromise: rotate all API keys, secrets, and OAuth tokens set in the plugin's email connectors, and block the published attacker IPs.