WordPress vulnerability database

Every CVE published for WordPress core, plugins and themes since January 2024: 29,758 vulnerabilities, 1,866 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 12, 2026.

Showing 451–454 of 454 vulnerabilities matching your filters

Known WordPress vulnerabilities, page 10 of 10
Severity Component Vulnerability Affected versions Published CVE Source
4.3 Medium Smart Slider 3 Plugin smart-slider-3 PHP Object Injection WordPress Smart Slider 3 Plugin <= 3.5.1.9 is vulnerable to PHP Object Injection ≤ 3.5.1.9 Fixed in 3.5.1.11 CVE-2022-45845 Patchstack
5.4 Medium Cart2Cart: Magento to WooCommerce Migration Plugin cart2cart-magento-to-woocommerce-migration Broken Access Control WordPress Cart2Cart: Magento to WooCommerce Migration Plugin <= 2.0.0 is vulnerable to Broken Access Control ≤ 2.0.0 CVE-2023-34379 Patchstack
4.3 Medium Ecwid Ecommerce Shopping Cart Plugin Cross-Site Request Forgery Arbitrary Plugin Settings Change via CSRF No login needed < 6.12.5 Fixed in 6.12.5 CVE-2023-6292 WPScan
4.3 Medium LightStart – Maintenance Mode, Coming Soon and Landing Page Builder Plugin wp-maintenance-mode Broken Access Control Maintenance Mode, Coming Soon and Landing Page Builder <= 2.6.8 - Missing Authorization ≤ 2.6.8 Fixed in 2.6.9 CVE-2023-7019 Wordfence

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 attacker needs no account, as the publisher's text states it, or as the score assumes when the text does not say.
Affected versions
The range the publisher marked as vulnerable. When the record also names the first fixed release, it is shown under the range. Some publishers only give the last affected version; when their references show the fix, the fixed release is the first one on wordpress.org after that version. 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