WordPress vulnerability database

Every CVE published for WordPress core, plugins and themes since January 2024: 29,070 vulnerabilities, 1,395 of them in the last 30 days. The list is updated every day from the CVE List.

Severity is the CVSS 3.1 base score. Select a band to list only those. Last updated October 6, 2026.

Showing 1–15 of 15 vulnerabilities matching your filters

Known WordPress vulnerabilities, page 1 of 1
Severity Component Vulnerability Affected versions Published CVE Source
7.5 High Uncanny Automator Plugin uncanny-automator Broken Access Control Missing Authorization to Authenticated (Subscriber+) Sensitive Integration Metadata Disclosure via Multiple AJAX Endpoints No login needed ≤ 7.3.2 CVE-2026-15025 Wordfence
7.6 High Uncanny Automator Plugin uncanny-automator SQL Injection ≤ 7.3.2 Fixed in 7.4.0 CVE-2026-65462 Patchstack
8.1 High Uncanny Automator Plugin uncanny-automator PHP Object Injection Unauthenticated PHP Object Injection to Arbitrary File Deletion via Forminator Submitted-Field Token No login needed ≤ 7.3.1.4 CVE-2026-15008 Wordfence
9.8 Critical Uncanny Automator Pro Plugin uncanny-automator-pro PHP Object Injection No login needed ≤ 7.3.0.6 Fixed in 7.3.0.7 CVE-2026-56057 Patchstack
8.1 High Uncanny Automator Plugin uncanny-automator PHP Object Injection No login needed ≤ 7.3.1.2 Fixed in 7.3.1.3 CVE-2026-56031 Patchstack
6.4 Medium Uncanny Automator – Easy Automation, Integration, Webhooks & Workflow Builder Plugin uncanny-automator Cross-Site Scripting Easy Automation, Integration, Webhooks & Workflow Builder Plugin <= 6.10.0.2 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode ≤ 6.10.0.2 CVE-2025-15522 Wordfence
4.3 Medium Uncanny Automator Plugin uncanny-automator Information Disclosure Sensitive Data Exposure ≤ 6.10.0 Fixed in 6.10.0 CVE-2025-66056 Patchstack
4.3 Medium Uncanny Automator Plugin uncanny-automator Broken Access Control ≤ 6.7.0.1 Fixed in 6.8.0 CVE-2025-58193 Patchstack
6.5 Medium Uncanny Automator Plugin uncanny-automator Broken Access Control No login needed ≤ 6.4.0.2 Fixed in 6.5.0 CVE-2025-48133 Patchstack
5.4 Medium Uncanny Automator Plugin uncanny-automator Broken Access Control Missing Authorization to Authenticated (Subscriber+) Plugin Settings Update ≤ 6.4.0.2 CVE-2025-4520 Wordfence
9.1 Critical Uncanny Automator Plugin uncanny-automator PHP Object Injection Unauthenticated PHP Object Injection in automator_api_decode_message Function No login needed ≤ 6.4.0.1 CVE-2025-3623 Wordfence
8.8 High Uncanny Automator Plugin uncanny-automator Broken Access Control Missing Authorization to Authenticated (Subscriber+) Privilege Escalation ≤ 6.3.0.2 CVE-2025-2075 Wordfence
5.5 Medium Uncanny Automator – Easy Automation, Integration, Webhooks & Workflow Builder Plugin uncanny-automator Server-Side Request Forgery Easy Automation, Integration, Webhooks & Workflow Builder Plugin <= 6.2 - Authenticated (Admin+) Server-Side Request Forgery via Webhook ≤ 6.2 CVE-2024-13838 Wordfence
5.3 Medium Uncanny Automator Pro Plugin uncanny-automator-pro Broken Access Control Unauthenticated License Settings Reset No login needed ≤ 5.3.0.0 Fixed in 5.3.0.1 CVE-2024-37119 Patchstack
5.3 Medium Uncanny Automator – Automate everything with the #1 no-code automation and integration Plugin uncanny-automator Information Disclosure WordPress Uncanny Automator Plugin <= 5.1.0.2 is vulnerable to Sensitive Data Exposure No login needed ≤ 5.1.0.2 Fixed in 5.1.0.3 CVE-2023-52151 Patchstack

About this data

Where it comes from
Each row is a record from the CVE List, published by the organization that handled the report: most often Wordfence, Patchstack or WPScan. The CVE ID links to that publisher's advisory.
What is included
CVEs published since January 1, 2024 for WordPress core, plugins and themes, premium ones included. Vulnerabilities that never received a CVE ID are not listed, and rejected CVEs are removed.
Severity
The CVSS 3.1 base score set by the publisher, or by CISA when the publisher gave none. "No login needed" means the score assumes an attacker without an account.
Affected versions
The range the publisher marked as vulnerable. When the record also names the first fixed release, it is shown under the range. If your version is newer than every affected one, that CVE does not apply to you.
Updates
Every day, after the CVE List publishes its end-of-day changes.

This website uses cookies to enhance your browsing experience and ensure the site functions properly. By continuing to use this site, you acknowledge and accept our use of cookies.

Accept All Accept Required Only