Critical security advisoryCriticalFlagged by our vulnerability database: PHP2Shell is on CISA’s exploited list. Most WordPress hosting runs PHP. See if your site is affectedFlagged by our vulnerability database: PHP2Shell is being exploited. DetailsExploited: PHP2Shell. Check your site
HuttenlocherTechnologies
Updated 9 h ago

Vulnerability database

Every flaw the U.S. government’s cybersecurity agency (CISA) has confirmed attackers are using, plus the new WordPress plugin and theme bugs published each day, sorted by what they mean for a small business. We refresh it twice a day. If you see something your website or office runs, tell us.

1,766exploited flaws on CISA’s list
36added in the last 30 days
526new WordPress flaws this week
391,181entries in the database

1,454 results · page 18 of 30

  • Jun 6, 2024SellKit – Funnel builder and checkout optimizer for WooCommerce to sell more, faster: Stored Cross-Site ScriptingCVE-2024-4608 · WordPress plugins & themes · reported by WordfenceMedium 6.4

    The SellKit – Funnel builder and checkout optimizer for WooCommerce to sell more, faster plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'id' parameter in all versions up to, and including, 1.9.8 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

    Product
    SellKit – Funnel builder and checkout optimizer for WooCommerce to sell more, faster
    Affected
    up to 1.9.8
    What to do
    Affects up to 1.9.8. Update SellKit – Funnel builder and checkout optimizer for WooCommerce to sell more, faster to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Jun 5, 2024Multiple plugins for WordPress utilizing the XootiX Framework are vulnerable to unauthorized modification of data due to a missing capability check on the 'impoCVE-2024-5324 · WordPress plugins & themes · reported by WordfenceHigh 8.8

    Multiple plugins for WordPress utilizing the XootiX Framework are vulnerable to unauthorized modification of data due to a missing capability check on the 'import_settings' function in various versions. This makes it possible for authenticated attackers, with Subscriber-level access and above, to change arbitrary options on affected sites. This can be used to enable new user registration and set the default role for new users to Administrator.

    What to do
    Update the plugin to the newest version.
  • Jun 4, 2024Claudio Sanches – Checkout Cielo for WooCommerce: Unauthorized modification of dataCVE-2024-1718 · WordPress plugins & themes · reported by WordfenceMedium 5.3

    The Claudio Sanches – Checkout Cielo for WooCommerce plugin for WordPress is vulnerable to unauthorized modification of data due to insufficient payment validation in the update_order_status() function in all versions up to, and including, 1.1.0. This makes it possible for unauthenticated attackers to update the status of orders to paid bypassing payment.

    Product
    Claudio Sanches – Checkout Cielo for WooCommerce
    Affected
    up to 1.1.0
    What to do
    Affects up to 1.1.0. Update Claudio Sanches – Checkout Cielo for WooCommerce to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 27, 2024KKProgressbar2 Free: Does not have CSRF checks in some placesCVE-2024-4535 · WordPress plugins & themes · reported by WPScanHigh 8.8

    The KKProgressbar2 Free WordPress plugin through 1.1.4.2 does not have CSRF checks in some places, which could allow attackers to make logged in users perform unwanted actions via CSRF attacks

    Product
    KKProgressbar2 Free
    Affected
    up to 1.1.4.2
    What to do
    Affects up to 1.1.4.2. Update KKProgressbar2 Free to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 27, 2024KKProgressbar2 Free: Does not have CSRF check in some placesCVE-2024-4534 · WordPress plugins & themes · reported by WPScanMedium 6.1

    The KKProgressbar2 Free WordPress plugin through 1.1.4.2 does not have CSRF check in some places, and is missing sanitisation as well as escaping, which could allow attackers to make logged in admin add Stored XSS payloads via a CSRF attack

    Product
    KKProgressbar2 Free
    Affected
    up to 1.1.4.2
    What to do
    Affects up to 1.1.4.2. Update KKProgressbar2 Free to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 27, 2024Business Card: Does not have CSRF checks in some placesCVE-2024-4532 · WordPress plugins & themes · reported by WPScanMedium 6.4

    The Business Card WordPress plugin through 1.0.0 does not have CSRF checks in some places, which could allow attackers to make logged in users perform unwanted actions such as deleting cards via CSRF attacks

    Product
    Business Card
    Affected
    up to 1.0.0
    What to do
    Affects up to 1.0.0. Update Business Card to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 27, 2024Business Card: Does not have CSRF checks in some placesCVE-2024-4531 · WordPress plugins & themes · reported by WPScanHigh 7.1

    The Business Card WordPress plugin through 1.0.0 does not have CSRF checks in some places, which could allow attackers to make logged in users perform unwanted actions such as editing cards via CSRF attacks

    Product
    Business Card
    Affected
    up to 1.0.0
    What to do
    Affects up to 1.0.0. Update Business Card to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 27, 2024Business Card: Does not have CSRF checks in some placesCVE-2024-4530 · WordPress plugins & themes · reported by WPScanMedium 6.3

    The Business Card WordPress plugin through 1.0.0 does not have CSRF checks in some places, which could allow attackers to make logged in users perform unwanted actions such as editing card categories via CSRF attacks

    Product
    Business Card
    Affected
    up to 1.0.0
    What to do
    Affects up to 1.0.0. Update Business Card to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 27, 2024Business Card: Does not have CSRF checks in some placesCVE-2024-4529 · WordPress plugins & themes · reported by WPScanMedium 5

    The Business Card WordPress plugin through 1.0.0 does not have CSRF checks in some places, which could allow attackers to make logged in users perform unwanted actions such as deleting card categories via CSRF attacks

    Product
    Business Card
    Affected
    up to 1.0.0
    What to do
    Affects up to 1.0.0. Update Business Card to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 17, 2024WP Express Checkout (Accept PayPal Payments): Improper Validation of Specified Quantity in InputCVE-2024-30527 · WordPress plugins & themes · reported by PatchstackHigh 7.5

    Improper Validation of Specified Quantity in Input vulnerability in Tips and Tricks HQ WP Express Checkout (Accept PayPal Payments) allows Manipulating Hidden Fields.This issue affects WP Express Checkout (Accept PayPal Payments): from n/a through 2.3.7.

    Product
    WP Express Checkout (Accept PayPal Payments)
    Affected
    up to 2.3.7
    What to do
    Affects up to 2.3.7. Update WP Express Checkout (Accept PayPal Payments) to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 17, 2024WooCommerce One Page Checkout: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')CVE-2023-35881 · WordPress plugins & themes · reported by PatchstackHigh 7.6

    Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in WooCommerce WooCommerce One Page Checkout allows PHP Local File Inclusion.This issue affects WooCommerce One Page Checkout: from n/a through 2.3.0.

    Product
    WooCommerce One Page Checkout
    Affected
    up to 2.3.0
    What to do
    Affects up to 2.3.0. Update WooCommerce One Page Checkout to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 17, 2024Conditional Checkout Fields for WooCommerce: Missing AuthorizationCVE-2022-45070 · WordPress plugins & themes · reported by PatchstackMedium 5.3

    Missing Authorization vulnerability in FmeAddons Conditional Checkout Fields for WooCommerce.This issue affects Conditional Checkout Fields for WooCommerce: from n/a through 1.2.3.

    Product
    Conditional Checkout Fields for WooCommerce
    Affected
    up to 1.2.3
    What to do
    Affects up to 1.2.3. Update Conditional Checkout Fields for WooCommerce to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 16, 2024Newsletter Popup: Does not have CSRF checkCVE-2024-3643 · WordPress plugins & themes · reported by WPScanHigh 8.8

    The Newsletter Popup WordPress plugin through 1.2 does not have CSRF check when deleting list, which could allow attackers to make logged in admins perform such action via a CSRF attack

    Product
    Newsletter Popup
    Affected
    up to 1.2
    What to do
    Affects up to 1.2. Update Newsletter Popup to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 16, 2024Newsletter Popup: Does not have CSRF checkCVE-2024-3642 · WordPress plugins & themes · reported by WPScanMedium 6.9

    The Newsletter Popup WordPress plugin through 1.2 does not have CSRF check when deleting subscriber, which could allow attackers to make logged in admins perform such action via a CSRF attack

    Product
    Newsletter Popup
    Affected
    up to 1.2
    What to do
    Affects up to 1.2. Update Newsletter Popup to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 15, 2024Base64 Encoder/Decoder: Does not have CSRF check in placeCVE-2024-3824 · WordPress plugins & themes · reported by WPScanMedium 5.5

    The Base64 Encoder/Decoder WordPress plugin through 0.9.2 does not have CSRF check in place when resetting its settings, which could allow attackers to make a logged in admin reset them via a CSRF attack

    Product
    Base64 Encoder/Decoder
    Affected
    up to 0.9.2
    What to do
    Affects up to 0.9.2. Update Base64 Encoder/Decoder to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 15, 2024Base64 Encoder/Decoder: Does not have CSRF checkCVE-2024-3823 · WordPress plugins & themes · reported by WPScanLow 2.4

    The Base64 Encoder/Decoder WordPress plugin through 0.9.2 does not have CSRF check when updating its settings, and is missing sanitisation as well as escaping, which could allow attackers to make logged in admin add Stored XSS payloads via a CSRF attack

    Product
    Base64 Encoder/Decoder
    Affected
    up to 0.9.2
    What to do
    Affects up to 0.9.2. Update Base64 Encoder/Decoder to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 15, 2024HL Twitter: Does not have CSRF checkCVE-2024-3631 · WordPress plugins & themes · reported by WPScanMedium 4.3

    The HL Twitter WordPress plugin through 2014.1.18 does not have CSRF check when unlinking twitter accounts, which could allow attackers to make logged in admins perform such actions via a CSRF attack

    Product
    HL Twitter
    Affected
    up to 2014.1.18
    What to do
    Affects up to 2014.1.18. Update HL Twitter to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 15, 2024HL Twitter: Does not have CSRF check in placeCVE-2024-3629 · WordPress plugins & themes · reported by WPScanLow 2.4

    The HL Twitter WordPress plugin through 2014.1.18 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them via a CSRF attack

    Product
    HL Twitter
    Affected
    up to 2014.1.18
    What to do
    Affects up to 2014.1.18. Update HL Twitter to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 15, 2024WP Prayer: Does not have CSRF checks in some placesCVE-2024-3407 · WordPress plugins & themes · reported by WPScanMedium 5.3

    The WP Prayer WordPress plugin through 2.0.9 does not have CSRF checks in some places, which could allow attackers to make logged in users perform unwanted actions via CSRF attacks

    Product
    WP Prayer
    Affected
    up to 2.0.9
    What to do
    Affects up to 2.0.9. Update WP Prayer to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 15, 2024WP Prayer: Does not have CSRF check in placeCVE-2024-3406 · WordPress plugins & themes · reported by WPScanHigh 8.8

    The WP Prayer WordPress plugin through 2.0.9 does not have CSRF check in place when updating its email settings, which could allow attackers to make a logged in admin change them via a CSRF attack

    Product
    WP Prayer
    Affected
    up to 2.0.9
    What to do
    Affects up to 2.0.9. Update WP Prayer to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 15, 2024WP Prayer: Does not have CSRF check in placeCVE-2024-3405 · WordPress plugins & themes · reported by WPScanHigh 7.6

    The WP Prayer WordPress plugin through 2.0.9 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them via a CSRF attack

    Product
    WP Prayer
    Affected
    up to 2.0.9
    What to do
    Affects up to 2.0.9. Update WP Prayer to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 14, 2024reCAPTCHA Jetpack: Does not have CSRF check in some placesCVE-2024-3941 · WordPress plugins & themes · reported by WPScanMedium 4.7

    The reCAPTCHA Jetpack WordPress plugin through 0.2.2 does not have CSRF check in some places, and is missing sanitisation as well as escaping, which could allow attackers to make logged-in admin add Stored XSS payloads via a CSRF attack.

    Product
    reCAPTCHA Jetpack
    Affected
    up to 0.2.2
    What to do
    Affects up to 0.2.2. Update reCAPTCHA Jetpack to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 14, 2024reCAPTCHA Jetpack: Does not have CSRF check in placeCVE-2024-3940 · WordPress plugins & themes · reported by WPScanHigh 8.8

    The reCAPTCHA Jetpack WordPress plugin through 0.2.2 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them via a CSRF attack

    Product
    reCAPTCHA Jetpack
    Affected
    up to 0.2.2
    What to do
    Affects up to 0.2.2. Update reCAPTCHA Jetpack to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 14, 2024Add Custom CSS and JS: Does not have CSRF check in some placesCVE-2024-3903 · WordPress plugins & themes · reported by WPScanHigh 7.1

    The Add Custom CSS and JS WordPress plugin through 1.20 does not have CSRF check in some places, and is missing sanitisation as well as escaping, which could allow attackers to make logged in as author and above add Stored XSS payloads via a CSRF attack

    Product
    Add Custom CSS and JS
    Affected
    up to 1.20
    What to do
    Affects up to 1.20. Update Add Custom CSS and JS to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 14, 2024LetterPress: Does not have CSRF checks in some placesCVE-2024-3590 · WordPress plugins & themes · reported by WPScanMedium 6.1

    The LetterPress WordPress plugin through 1.2.2 does not have CSRF checks in some places, which could allow attackers to make logged in users perform unwanted actions via CSRF attacks, such as delete arbitrary subscribers

    Product
    LetterPress
    Affected
    up to 1.2.2
    What to do
    Affects up to 1.2.2. Update LetterPress to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 14, 2024UnGallery: Does not have CSRF check in some placesCVE-2024-3582 · WordPress plugins & themes · reported by WPScanMedium 4.8

    The UnGallery WordPress plugin through 2.2.4 does not have CSRF check in some places, and is missing sanitisation as well as escaping, which could allow attackers to make logged in admin add Stored XSS payloads via a CSRF attack

    Product
    UnGallery
    Affected
    up to 2.2.4
    What to do
    Affects up to 2.2.4. Update UnGallery to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 14, 2024Custom WooCommerce Checkout Fields Editor: Missing AuthorizationCVE-2024-33956 · WordPress plugins & themes · reported by PatchstackMedium 4.3

    Missing Authorization vulnerability in ThemeLocation Custom WooCommerce Checkout Fields Editor.This issue affects Custom WooCommerce Checkout Fields Editor: from n/a through 1.3.0.

    Product
    Custom WooCommerce Checkout Fields Editor
    Affected
    up to 1.3.0
    What to do
    Affects up to 1.3.0. Update Custom WooCommerce Checkout Fields Editor to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 6, 2024MF Gig Calendar: Does not have CSRF checks in some placesCVE-2024-3756 · WordPress plugins & themes · reported by WPScanHigh 7.5

    The MF Gig Calendar WordPress plugin through 1.2.1 does not have CSRF checks in some places, which could allow attackers to make logged in Contributors and above delete arbitrary events via a CSRF attack

    Product
    MF Gig Calendar
    Affected
    up to 1.2.1
    What to do
    Affects up to 1.2.1. Update MF Gig Calendar to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 2, 2024SmartCrawl WordPress SEO checker, SEO analyzer, SEO optimizer: Unauthorized ld+json description injectionCVE-2024-3287 · WordPress plugins & themes · reported by WordfenceMedium 5.3

    The SmartCrawl WordPress SEO checker, SEO analyzer, SEO optimizer plugin for WordPress is vulnerable to unauthorized ld+json description injection due to a missing capability check on the save_settings function in all versions up to, and including, 3.10.2. This makes it possible for unauthenticated attackers to save schema types.

    Product
    SmartCrawl WordPress SEO checker, SEO analyzer, SEO optimizer
    Affected
    up to 3.10.2
    What to do
    Affects up to 3.10.2. Update SmartCrawl WordPress SEO checker, SEO analyzer, SEO optimizer to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 2, 2024Where Did You Hear About Us Checkout Field for WooCommerce: Stored Cross-Site ScriptingCVE-2024-2752 · WordPress plugins & themes · reported by WordfenceMedium 5.5

    The Where Did You Hear About Us Checkout Field for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via order meta in all versions up to, and including, 1.3.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with shop manager-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

    Product
    Where Did You Hear About Us Checkout Field for WooCommerce
    Affected
    up to 1.3.1
    What to do
    Affects up to 1.3.1. Update Where Did You Hear About Us Checkout Field for WooCommerce to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 2, 20242Checkout Payment Gateway for WooCommerce: Unauthorized modification of dataCVE-2024-0629 · WordPress plugins & themes · reported by WordfenceMedium 5.3

    The 2Checkout Payment Gateway for WooCommerce plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the sniff_ins function in all versions up to, and including, 6.2. This makes it possible for unauthenticated attackers to make changes to orders and mark them as paid.

    Product
    2Checkout Payment Gateway for WooCommerce
    Affected
    up to 6.2
    What to do
    Affects up to 6.2. Update 2Checkout Payment Gateway for WooCommerce to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 2, 2024Counter Box: Does not have CSRF checks in some bulk actionsCVE-2024-3481 · WordPress plugins & themes · reported by WPScanMedium 5.2

    The Counter Box WordPress plugin before 1.2.4 does not have CSRF checks in some bulk actions, which could allow attackers to make logged in admins perform unwanted actions, such deleting counters via CSRF attacks

    Product
    Counter Box
    Fixed in
    1.2.4
    What to do
    Update Counter Box to 1.2.4 or newer.
  • May 2, 2024Herd Effects: Does not have CSRF checks in some bulk actionsCVE-2024-3478 · WordPress plugins & themes · reported by WPScanMedium 6.1

    The Herd Effects WordPress plugin before 5.2.7 does not have CSRF checks in some bulk actions, which could allow attackers to make logged in admins perform unwanted actions, such as deleting effects via CSRF attacks

    Product
    Herd Effects
    Fixed in
    5.2.7
    What to do
    Update Herd Effects to 5.2.7 or newer.
  • May 2, 2024Popup Box: Does not have CSRF checks in some bulk actionsCVE-2024-3477 · WordPress plugins & themes · reported by WPScanMedium 4.3

    The Popup Box WordPress plugin before 2.2.7 does not have CSRF checks in some bulk actions, which could allow attackers to make logged in admins perform unwanted actions, such as deleting popups via CSRF attacks

    Product
    Popup Box
    Fixed in
    2.2.7
    What to do
    Update Popup Box to 2.2.7 or newer.
  • May 2, 2024Side Menu Lite: Does not have CSRF checks in some bulk actionsCVE-2024-3476 · WordPress plugins & themes · reported by WPScanHigh 8.8

    The Side Menu Lite WordPress plugin before 4.2.1 does not have CSRF checks in some bulk actions, which could allow attackers to make logged in admins perform unwanted actions, such as deleting buttons via CSRF attacks

    Product
    Side Menu Lite
    Fixed in
    4.2.1
    What to do
    Update Side Menu Lite to 4.2.1 or newer.
  • May 2, 2024Sticky Buttons: Does not have CSRF checks in some bulk actionsCVE-2024-3475 · WordPress plugins & themes · reported by WPScanHigh 7.5

    The Sticky Buttons WordPress plugin before 3.2.4 does not have CSRF checks in some bulk actions, which could allow attackers to make logged in admins perform unwanted actions, such as deleting buttons via CSRF attacks

    Product
    Sticky Buttons
    Fixed in
    3.2.4
    What to do
    Update Sticky Buttons to 3.2.4 or newer.
  • May 2, 2024Wow Skype Buttons: Does not have CSRF checks in some bulk actionsCVE-2024-3474 · WordPress plugins & themes · reported by WPScanHigh 8.8

    The Wow Skype Buttons WordPress plugin before 4.0.4 does not have CSRF checks in some bulk actions, which could allow attackers to make logged in admins perform unwanted actions, such as deleting buttons via CSRF attacks

    Product
    Wow Skype Buttons
    Fixed in
    4.0.4
    What to do
    Update Wow Skype Buttons to 4.0.4 or newer.
  • May 2, 2024Modal Window: Does not have CSRF check in placeCVE-2024-3472 · WordPress plugins & themes · reported by WPScanMedium 5.9

    The Modal Window WordPress plugin before 5.3.10 does not have CSRF check in place when bulk deleting modals, which could allow attackers to make a logged in admin delete them via a CSRF attack

    Product
    Modal Window
    Fixed in
    5.3.10
    What to do
    Update Modal Window to 5.3.10 or newer.
  • May 2, 2024Button Generator: Does not have CSRF check in placeCVE-2024-3471 · WordPress plugins & themes · reported by WPScanLow 3.4

    The Button Generator WordPress plugin before 3.0 does not have CSRF check in place when bulk deleting, which could allow attackers to make a logged in admin delete buttons via a CSRF attack

    Product
    Button Generator
    Fixed in
    3.0
    What to do
    Update Button Generator to 3.0 or newer.
  • May 2, 2024Float menu: Does not have CSRF check in its bulk actionsCVE-2024-2405 · WordPress plugins & themes · reported by WPScanMedium 4.5

    The Float menu WordPress plugin before 6.0.1 does not have CSRF check in its bulk actions, which could allow attackers to make logged in admin delete arbitrary menu via a CSRF attack.

    Product
    Float menu
    Fixed in
    6.0.1
    What to do
    Update Float menu to 6.0.1 or newer.
  • Apr 26, 2024MM-email2image: Does not have CSRF check in some placesCVE-2024-3076 · WordPress plugins & themes · reported by WPScanLow 3.8

    The MM-email2image WordPress plugin through 0.2.5 does not have CSRF check in some places, and is missing sanitisation as well as escaping, which could allow attackers to make logged in admin add Stored XSS payloads via a CSRF attack

    Product
    MM-email2image
    Affected
    up to 0.2.5
    What to do
    Affects up to 0.2.5. Update MM-email2image to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Apr 26, 2024ENL Newsletter: Does not have CSRF checks in some placesCVE-2024-3059 · WordPress plugins & themes · reported by WPScanMedium 5.7

    The ENL Newsletter WordPress plugin through 1.0.1 does not have CSRF checks in some places, which could allow attackers to make logged in admins delete arbitrary Campaigns via a CSRF attack

    Product
    ENL Newsletter
    Affected
    up to 1.0.1
    What to do
    Affects up to 1.0.1. Update ENL Newsletter to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Apr 26, 2024ENL Newsletter: Does not have CSRF check in some placesCVE-2024-3058 · WordPress plugins & themes · reported by WPScanMedium 5.4

    The ENL Newsletter WordPress plugin through 1.0.1 does not have CSRF check in some places, and is missing sanitisation as well as escaping, which could allow attackers to make logged in admin add Stored XSS payloads via a CSRF attack

    Product
    ENL Newsletter
    Affected
    up to 1.0.1
    What to do
    Affects up to 1.0.1. Update ENL Newsletter to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Apr 26, 2024Salon booking system: Does not have CSRF check in placeCVE-2024-2429 · WordPress plugins & themes · reported by WPScanMedium 4.3

    The Salon booking system WordPress plugin through 9.6.5 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them via a CSRF attack

    Product
    Salon booking system
    Affected
    up to 9.6.5
    What to do
    Affects up to 9.6.5. Update Salon booking system to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Apr 24, 2024Checkout Mestres WP: Improper AuthenticationCVE-2023-51472 · WordPress plugins & themes · reported by PatchstackCritical 9.8

    Improper Authentication vulnerability in Mestres do WP Checkout Mestres WP allows Privilege Escalation.This issue affects Checkout Mestres WP: from n/a through 7.1.9.7.

    Product
    Checkout Mestres WP
    Affected
    up to 7.1.9.7
    What to do
    Affects up to 7.1.9.7. Update Checkout Mestres WP to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Apr 24, 2024Checkout Mestres WP: Improper AuthenticationCVE-2023-51471 · WordPress plugins & themes · reported by PatchstackHigh 8.2

    Improper Authentication vulnerability in Mestres do WP Checkout Mestres WP allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Checkout Mestres WP: from n/a through 7.1.9.7.

    Product
    Checkout Mestres WP
    Affected
    up to 7.1.9.7
    What to do
    Affects up to 7.1.9.7. Update Checkout Mestres WP to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Apr 24, 2024WP ADA Compliance Check Basic: Cross-Site Request Forgery (CSRF)CVE-2024-32947 · WordPress plugins & themes · reported by PatchstackMedium 4.3

    Cross-Site Request Forgery (CSRF) vulnerability in AlumniOnline Web Services LLC WP ADA Compliance Check Basic.This issue affects WP ADA Compliance Check Basic: from n/a through 3.1.3.

    Product
    WP ADA Compliance Check Basic
    Affected
    up to 3.1.3
    What to do
    Affects up to 3.1.3. Update WP ADA Compliance Check Basic to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Apr 18, 2024WP Stripe Checkout: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')CVE-2024-32571 · WordPress plugins & themes · reported by PatchstackMedium 6.5

    Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in naa986 WP Stripe Checkout allows Stored XSS.This issue affects WP Stripe Checkout: from n/a through 1.2.2.41.

    Product
    WP Stripe Checkout
    Affected
    up to 1.2.2.41
    What to do
    Affects up to 1.2.2.41. Update WP Stripe Checkout to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Apr 15, 2024Simple Buttons Creator: Does not have CSRF checks in some placesCVE-2024-2858 · WordPress plugins & themes · reported by WPScanMedium 4.8

    The Simple Buttons Creator WordPress plugin through 1.04 does not have CSRF checks in some places, which could allow attackers to make logged in users perform unwanted actions via CSRF attacks

    Product
    Simple Buttons Creator
    Affected
    up to 1.04
    What to do
    Affects up to 1.04. Update Simple Buttons Creator to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Apr 15, 2024Advanced Search: Does not have CSRF checks in some placesCVE-2024-2739 · WordPress plugins & themes · reported by WPScanHigh 8.7

    The Advanced Search WordPress plugin through 1.1.6 does not have CSRF checks in some places, which could allow attackers to make logged in users perform unwanted actions via CSRF attacks

    Product
    Advanced Search
    Affected
    up to 1.1.6
    What to do
    Affects up to 1.1.6. Update Advanced Search to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.

Where this comes from: the exploited list is CISA’s Known Exploited Vulnerabilities catalog. Everything else is the whole National Vulnerability Database, where each record is published by the team that found the bug (Wordfence, Patchstack, WPScan, the vendors themselves and others); we show who. Exploit odds are FIRST’s EPSS, updated daily. Titles and categories are ours, so check the linked record before acting on a detail. For a write-up of the big ones, see our advisories. Every vendor, and every WordPress plugin and theme with a recorded flaw, also has its own page. All of it is free to reuse as JSON, CSV or RSS.

Weekly security brief

The flaws that hit local websites, every Friday.

One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.

Get in touch

Tell us what you're building.

A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.

01The person who'll do the work writes back
02A short call, then a written plan with the price
03Nothing starts until you say yes
04Hacked or down right now? Call, and we pick up the same day
843-331-6339

Not ready to talk yet? Run the free website check and see what Google sees.

What do you need?
Build
Grow
Protect
Urgent

No newsletter, no sales sequence. Just a reply.