Sovra Recon·Updated November 6, 2026

WordPress vulnerabilities: what to know right now

WordPress: the world's most widely used CMS, where most vulnerabilities come from plugins and themes. This page continuously tracks the vulnerabilities affecting it, based on our security news and official databases (NVD, CISA's catalog of exploited vulnerabilities).

At a glance

In the news, the most significant WordPress vulnerability tracked in our security news is CVE-2026-81648 (critical severity, CVSS score 10.0).

As of November 6, 2026, 7 WordPress vulnerabilities are listed in CISA's catalog of vulnerabilities exploited by attackers. The most recent, CVE-2026-119977, was added on November 3, 2026.

Among the WordPress vulnerabilities published in the last 7 days in the NVD, the most severe is CVE-2026-124822 (score 10.0), published on November 13, 2026.

Are you affected? In the admin, go to Dashboard → Updates: the core version and every plugin's version are listed there. A plugin named in an alert must be updated or deactivated.

Actively exploited

WordPress vulnerabilities exploited by attackers

CISA's Known Exploited Vulnerabilities (KEV) catalog only lists vulnerabilities whose real-world exploitation has been confirmed. These are the first ones to patch.

CVEProductDate addedRansomware
CVE-2026-119977

WordPress WordPress Core Time-of-check Time-of-use (TOCTOU) Race Condition Vulnerability. WordPress WordPress Core contains a time-of-check time-of-use (TOCTOU) race condition vulnerability that could allow unauthenticated attackers to execute code on the server during the upgrade window. This is due to predictable, web-accessible staging paths used during full-package core upgrades.

WordPress CoreNovember 3, 2026Not reported
CVE-2026-87902

WordPress Core Remote File Inclusion Vulnerability. WordPress Core contains a remote file inclusion vulnerability which could allow an unauthenticated attacker to make page-template resolution include a chosen readable local `.php` file outside the active theme directories, leading to remote code execution.

CoreSeptember 25, 2026Not reported
CVE-2026-60137

WordPress Core SQL Injection Vulnerability. WordPress Core contains a SQL injection vulnerability when a plugin or theme passes untrusted input to the parameter. This vulnerability can be chained with CVE-2026-63030 to allow an unauthenticated attacker to gain remote code execution on default WordPress installations.

CoreJuly 21, 2026Not reported
CVE-2026-63030

WordPress Core Interpretation Conflict Vulnerability. WordPress Core contains an interpretation conflict vulnerability that could allow an attacker to perform SQL Injection and achieve Remote Code Execution. This vulnerability can be chained with CVE-2026-60137.

CoreJuly 21, 2026Not reported
CVE-2020-25213

WordPress File Manager Plugin Remote Code Execution Vulnerability. WordPress File Manager plugin contains a remote code execution vulnerability that allows unauthenticated users to execute PHP code and upload malicious files on a target site.

File Manager PluginNovember 3, 2021Not reported
CVE-2020-11738

WordPress Snap Creek Duplicator Plugin File Download Vulnerability. WordPress Snap Creek Duplicator plugin contains a file download vulnerability when an administrator creates a new copy of their site that allows an attacker to download the generated files from their Wordpress dashboard. This vulnerability affects Duplicator and Dulplicator Pro.

Snap Creek Duplicator PluginNovember 3, 2021Not reported
CVE-2019-9978

WordPress Social Warfare Plugin Cross-Site Scripting (XSS) Vulnerability. WordPress Social Warfare plugin contains a cross-site scripting (XSS) vulnerability that allows for remote code execution. This vulnerability affects Social Warfare and Social Warfare Pro.

Social Warfare PluginNovember 3, 2021Not reported

New CVEs

WordPress vulnerabilities published in the last 7 days

  • CVE-2026-124822published November 13, 2026The Easy DragDrop File Uploader WordPress plugin before 1.1.10 does not validate a user-supplied path before deleting it, allowing unauthenticated users to delete arbitrary files and directories on the server, such as wp-config.php.Critical10.0
  • CVE-2026-124815published November 12, 2026The Clockinator Lite WordPress plugin before 1.1.0 does not restrict access to several of its record deletion actions, and uses a user-supplied table name in a SQL query without validating or escaping it, allowing unauthenticated users to perform SQL injection attacks, deleting data from any database table and extracting sensitive information such as password hashes.Critical10.0
  • CVE-2026-127048published November 15, 2026The Custom Block Builder WordPress plugin before 3.0.0 does not properly deny unauthorised requests to its REST routes, as its permission checks return a non-error response that WordPress treats as granted, allowing unauthenticated users to execute arbitrary PHP code on the server.Critical9.8
  • CVE-2026-110960published November 15, 2026The Auth Armor WordPress plugin through 1.0.3 does not require authentication on several handlers available to logged-out users, which leak the site's stored API credentials and allow an unauthenticated attacker to reset an administrator's enrollment and take over that administrator account.Critical9.8
  • CVE-2026-19907published November 14, 2026The Shipo plugin for WordPress is vulnerable to Authentication Bypass in versions 1.6 through 1.8.0. This is due to the `authenticate_rest_user()` function parsing the `LOGGED_IN_COOKIE` value and authenticating the named user without verifying the cookie's cryptographic signature. The function's intended `/wp-json/shipo/` route restriction can also be bypassed by placing that substring in the query string of an unrelated REST endpoint. This makes it possible for unauthenticated attackers who know an existing username to impersonate that user, including an administrator, and perform authorized actions through the REST API, including creating another administrator account.Critical9.8
  • CVE-2026-120522published November 14, 2026The Cloud Storage Manager for Fluent Forms – Google Drive, Dropbox, OneDrive, S3 Uploads plugin for WordPress is vulnerable to Arbitrary File Write in all versions up to, and including, 1.2.0. This is due to missing authorization checks on the `connection/{driver}/save` and `/download/single-file` REST endpoints, combined with insufficient path validation in the Google Drive `downloadFile()` function, where the Google Drive metadata `name` value is concatenated into a local path without `basename()`, `sanitize_file_name()`, or canonical path validation. This makes it possible for unauthenticated attackers to store attacker-controlled Google Drive credentials, trigger a download of an attacker-owned file whose provider-returned filename contains path traversal, and write attacker-controlled content outside the intended `downloads` directory. When the written file has a PHP extension and lands in a web-accessible location, this can lead to remote code execution.Critical9.8
  • CVE-2026-125855published November 13, 2026Deserialization of Untrusted Data vulnerability in Elextensions ELEX WordPress HelpDesk & Customer Ticketing System elex-helpdesk-customer-support-ticket-system allows Object Injection.This issue affects ELEX WordPress HelpDesk & Customer Ticketing System: from n/a through 3.3.9.Critical9.8
  • CVE-2026-124814published November 12, 2026The Ultimate Addons for Elementor Forms WordPress plugin before 1.0.8 does not properly validate the extension of uploaded files in its bundled file upload field, allowing unauthenticated users to upload arbitrary files such as PHP scripts and achieve remote code execution.Critical9.8
  • CVE-2026-123695published November 11, 2026The Security For WooCommerce WordPress plugin through 1.0.16 does not restrict access to several of its REST API routes, allowing unauthenticated users to generate login tokens for every user and then retrieve them, and so log in as any user, including administrators.Critical9.8
  • CVE-2026-121497published November 11, 2026The AskAny WordPress plugin before 2.2.0 does not validate the extension or content of files attached to chat messages, trusting the browser-supplied file type instead, which allows unauthenticated users to upload PHP files and execute arbitrary code when visitor attachments are enabled.Critical9.8
  • CVE-2026-124672published November 16, 2026The Burst Statistics WordPress plugin before 3.7.5 does not verify that a request is actually being routed to its own REST API before unloading every other active plugin for that request, allowing unauthenticated attackers to have requests processed with other plugins' protections (such as REST access restrictions, hidden login pages and two-factor authentication) switched off, and to cause other plugins' scheduled tasks to be discarded.High7.3

In our security news

Recent WordPress vulnerabilities

CVESeverityExploited (CISA)Published
CVE-2026-81648

The CryptoPayment Gateway WordPress plugin from 1.2.1 to 1.2.2 does not apply an authorization check on one of its AJAX endpoints, allowing unauthenticated users to invoke administrative operations, including deleting arbitrary files on the server, overwriting the payment gateway configuration and recovering stored wallet credentials in cleartext.

Critical10.0Not reportedSeptember 13, 2026

Sources: NIST's National Vulnerability Database (NVD) for the CVSS score, CISA's Known Exploited Vulnerabilities (KEV) catalog for active exploitation. Official descriptions in their original wording.

Security news

WordPress news

A WordPress vulnerability in your environment?

Patching a known CVE is not enough: our AI agents actually attack your applications and hand you proof of every open door.