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 51–66 of 66 vulnerabilities matching your filters

Known WordPress vulnerabilities, page 2 of 2
Severity Component Vulnerability Affected versions Published CVE Source
6.5 Medium Stripe Donation Plugin bin-stripe-donation Cross-Site Scripting ≤ 1.2.5 CVE-2024-53752 Patchstack
6.1 Medium Payments Plugin and Checkout Plugin for WooCommerce: Stripe, PayPal, Square, Authorize.net Plugin peachpay-for-woocommerce Cross-Site Scripting Reflected Cross-Site Scripting No login needed ≤ 1.112.0 Fixed in 1.114.0 CVE-2024-11362 Wordfence
6.5 Medium Sell Media File with Stripe Plugin sell-media-file Cross-Site Scripting Stored Cross Site Scripting (XSS) ≤ 1.0.6 CVE-2024-51892 Patchstack
6.5 Medium Pay With Stripe Plugin payments-stripe-gateway Cross-Site Scripting ≤ 1.2.1 CVE-2024-51918 Patchstack
6.1 Medium Contact Form 7 - PayPal & Stripe Add-on Plugin contact-form-7-paypal-add-on Cross-Site Scripting PayPal & Stripe Add-on <= 2.3.1 - Reflected Cross-Site Scripting No login needed ≤ 2.3.1 CVE-2024-10683 Wordfence
5.3 Medium AidWP Plugin wp-stripe-donation Broken Access Control No login needed ≤ 3.2.3 Fixed in 3.2.4 CVE-2024-50459 Patchstack
4.3 Medium Stripe Payments For WooCommerce by Checkout Plugin checkout-plugins-stripe-woo Cross-Site Request Forgery No login needed ≤ 1.9.1 Fixed in 1.9.2 CVE-2024-43316 Patchstack
4.7 Medium Easy PayPal Buy Now Button Plugin wp-ecommerce-paypal Open Redirect No login needed ≤ 1.9 Fixed in 1.9.1 CVE-2024-43236 Patchstack
5.4 Medium Accept Stripe Payments Plugin stripe-payments Cross-Site Scripting Authenticated (Contributor+) Stored Cross-Site Scripting via accept_stripe_payment_ng Shortcode ≤ 2.0.86 CVE-2024-7353 Wordfence
5.3 Medium Stripe Payments Plugin stripe-payments Content Injection No login needed ≤ 2.0.79 Fixed in 2.0.80 CVE-2023-48285 Patchstack
6.5 Medium WP Stripe Checkout Plugin wp-stripe-checkout Cross-Site Scripting ≤ 1.2.2.41 Fixed in 1.2.2.42 CVE-2024-32571 Patchstack
5.4 Medium WooCommerce Stripe Payment Gateway Plugin woocommerce-gateway-stripe Cross-Site Request Forgery No login needed ≤ 7.6.0 Fixed in 7.6.1 CVE-2023-44999 Patchstack
5.4 Medium Easy PayPal & Stripe Buy Now Button Plugin wp-ecommerce-paypal Cross-Site Request Forgery WordPress Easy PayPal Buy Now Button Plugin <= 1.8.1 is vulnerable to Cross Site Request Forgery (CSRF) No login needed ≤ 1.8.1 Fixed in 1.8.2 CVE-2023-51683 Patchstack
4.3 Medium Easy PayPal & Stripe Buy Now Button Plugin wp-ecommerce-paypal Cross-Site Request Forgery PayPal & Stripe Add-on <= 2.1 - Cross-Site Request Forgery to Settings Update No login needed ≤ 1.8.3, ≤ 2.1 CVE-2024-1719 Wordfence
5.3 Medium Paid Membership Subscriptions – Effortless Memberships, Recurring Payments & Content Restriction Plugin paid-member-subscriptions Broken Access Control Effortless Memberships, Recurring Payments & Content Restriction <= 2.11.1 - Missing Authorization via pms_stripe_connect_handle_authorization_return No login needed ≤ 2.11.1 Fixed in 2.11.2 CVE-2024-1389 Wordfence
5.4 Medium GiveWP Plugin give Cross-Site Request Forgery Cross-Site Request Forgery to Stripe Integration Deletion No login needed ≤ 2.33.3 Fixed in 2.33.4 CVE-2023-4248 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