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 3 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,764exploited flaws on CISA’s list
35added in the last 30 days
472new WordPress flaws this week
390,714entries in the database

596 results · page 7 of 12

  • Jul 12, 2024ContentLock: Does not have CSRF check in placeCVE-2024-6022 · WordPress plugins & themes · reported by WPScanHigh 8.8

    The ContentLock WordPress plugin through 1.0.3 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
    ContentLock
    Affected
    up to 1.0.3
    What to do
    Affects up to 1.0.3. Update ContentLock to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Jul 11, 2024VikRentCar Car Rental Management System: Does not have CSRF checks in some placesCVE-2024-1845 · WordPress plugins & themes · reported by WPScanHigh 8.8

    The VikRentCar Car Rental Management System WordPress plugin before 1.3.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
    VikRentCar Car Rental Management System
    Fixed in
    1.3.2
    What to do
    Update VikRentCar Car Rental Management System to 1.3.2 or newer.
  • Jul 3, 2024WPQA Builder: Does not have CSRF checks in some placesCVE-2024-2376 · WordPress plugins & themes · reported by WPScanHigh 8.8

    The WPQA Builder WordPress plugin before 6.1.1 does not have CSRF checks in some places, which could allow attackers to make logged in users perform unwanted actions via CSRF attacks

    Product
    WPQA Builder
    Fixed in
    6.1.1
    What to do
    Update WPQA Builder to 6.1.1 or newer.
  • Jul 3, 2024Himer: Does not have CSRF checks in some placesCVE-2024-2235 · WordPress plugins & themes · reported by WPScanMedium 4.3

    The Himer WordPress theme before 2.1.1 does not have CSRF checks in some places, which could allow attackers to make users vote on any polls, including those they don't have access to via a CSRF attack

    Product
    Himer
    Fixed in
    2.1.1
    What to do
    Update Himer to 2.1.1 or newer.
  • Jul 3, 2024Himer: Does not have CSRF checks in some placesCVE-2024-2233 · WordPress plugins & themes · reported by WPScanMedium 4.3

    The Himer WordPress theme before 2.1.1 does not have CSRF checks in some places, which could allow attackers to make logged in users perform unwanted actions via CSRF attacks. These include declining and accepting group invitations or leaving a group

    Product
    Himer
    Fixed in
    2.1.1
    What to do
    Update Himer to 2.1.1 or newer.
  • Jul 3, 2024Himer: Does not have CSRF checks in some placesCVE-2024-2040 · WordPress plugins & themes · reported by WPScanMedium 4.3

    The Himer WordPress theme before 2.1.1 does not have CSRF checks in some places, which could allow attackers to make users join private groups via a CSRF attack

    Product
    Himer
    Fixed in
    2.1.1
    What to do
    Update Himer to 2.1.1 or newer.
  • Jul 2, 2024sitetweet: Does not have CSRF check in some placesCVE-2024-5767 · WordPress plugins & themes · reported by WPScanHigh 8.8

    The sitetweet WordPress plugin through 0.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
    sitetweet
    Affected
    up to 0.2
    What to do
    Affects up to 0.2. Update sitetweet to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Jun 26, 2024Muslim Prayer Time BD: Does not have CSRF check in placeCVE-2024-4758 · WordPress plugins & themes · reported by WPScanHigh 7.6

    The Muslim Prayer Time BD WordPress plugin through 2.4 does not have CSRF check in place when reseting its settings, which could allow attackers to make a logged in admin reset them via a CSRF attack

    Product
    Muslim Prayer Time BD
    Affected
    up to 2.4
    What to do
    Affects up to 2.4. Update Muslim Prayer Time BD to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Jun 25, 2024Logo Manager For Enamad: Does not have CSRF check in some placesCVE-2024-4757 · WordPress plugins & themes · reported by WPScanHigh 8.1

    The Logo Manager For Enamad WordPress plugin through 0.7.0 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
    Logo Manager For Enamad
    Affected
    up to 0.7.0
    What to do
    Affects up to 0.7.0. Update Logo Manager For Enamad to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Jun 21, 2024Interface: Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting')CVE-2024-35758 · WordPress plugins & themes · reported by PatchstackMedium 6.5

    Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Theme Horse Interface allows Stored XSS.This issue affects Interface: from n/a through 3.1.0.

    Product
    Interface
    Affected
    up to 3.1.0
    What to do
    Affects up to 3.1.0. Update Interface to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Jun 21, 2024WP Logs Book: Does not have CSRF check in placeCVE-2024-4474 · WordPress plugins & themes · reported by WPScanMedium 4.3

    The WP Logs Book WordPress plugin through 1.0.1 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 Logs Book
    Affected
    up to 1.0.1
    What to do
    Affects up to 1.0.1. Update WP Logs Book to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Jun 19, 2024Replace Image: Insecure Direct Object ReferenceCVE-2024-4873 · WordPress plugins & themes · reported by WordfenceMedium 4.3

    The Replace Image plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 1.1.10 via the image replacement functionality due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Author-level access and above, to replace images uploaded by higher level users such as admins.

    Product
    Replace Image
    Affected
    up to 1.1.10
    What to do
    Affects up to 1.1.10. Update Replace Image to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Jun 14, 2024Inquiry cart: Does not have CSRF check in some placesCVE-2024-5155 · WordPress plugins & themes · reported by WPScanMedium 6.1

    The Inquiry cart WordPress plugin through 3.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
    Inquiry cart
    Affected
    up to 3.4.2
    What to do
    Affects up to 3.4.2. Update Inquiry cart to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Jun 14, 2024WP Prayer II: Does not have CSRF check in placeCVE-2024-4751 · WordPress plugins & themes · reported by WPScanMedium 4.3

    The WP Prayer II WordPress plugin through 2.4.7 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 II
    Affected
    up to 2.4.7
    What to do
    Affects up to 2.4.7. Update WP Prayer II to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Jun 14, 2024WP Prayer II: Does not have CSRF check in placeCVE-2024-4480 · WordPress plugins & themes · reported by WPScanMedium 6.1

    The WP Prayer II WordPress plugin through 2.4.7 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 II
    Affected
    up to 2.4.7
    What to do
    Affects up to 2.4.7. Update WP Prayer II to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Jun 14, 2024AZAN: Does not have CSRF check in some placesCVE-2024-3993 · WordPress plugins & themes · reported by WPScanMedium 4.6

    The AZAN Plugin WordPress plugin through 0.6 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
    AZAN
    Affected
    up to 0.6
    What to do
    Affects up to 0.6. Update AZAN to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Jun 14, 2024Similarity: Does not have CSRF check in some placesCVE-2024-3972 · WordPress plugins & themes · reported by WPScanMedium 4.3

    The Similarity WordPress plugin through 3.0 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
    Similarity
    Affected
    up to 3.0
    What to do
    Affects up to 3.0. Update Similarity to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Jun 14, 2024Similarity: Does not have CSRF check in placeCVE-2024-3971 · WordPress plugins & themes · reported by WPScanMedium 4.3

    The Similarity WordPress plugin through 3.0 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
    Similarity
    Affected
    up to 3.0
    What to do
    Affects up to 3.0. Update Similarity to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Jun 14, 2024Pray For Me: Does not have CSRF check in placeCVE-2024-3965 · WordPress plugins & themes · reported by WPScanMedium 5.4

    The Pray For Me WordPress plugin through 1.0.4 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
    Pray For Me
    Affected
    up to 1.0.4
    What to do
    Affects up to 1.0.4. Update Pray For Me to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Jun 13, 2024Search & Replace: Does not sanitize and escape a parameter before using it in a SQL statementCVE-2024-4145 · WordPress plugins & themes · reported by WPScanHigh 7.2

    The Search & Replace WordPress plugin before 3.2.2 does not sanitize and escape a parameter before using it in a SQL statement, allowing admins to perform SQL injection attacks (such as within a multi-site network).

    Product
    Search & Replace
    Fixed in
    3.2.2
    What to do
    Update Search & Replace to 3.2.2 or newer.
  • Jun 11, 2024WC Marketplace: Missing AuthorizationCVE-2024-24703 · WordPress plugins & themes · reported by PatchstackHigh 8.6

    Missing Authorization vulnerability in MultiVendorX WC Marketplace.This issue affects WC Marketplace: from n/a through 4.0.25.

    Product
    WC Marketplace
    Affected
    up to 4.0.25
    What to do
    Affects up to 4.0.25. Update WC Marketplace to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Jun 9, 2024WC Marketplace: Missing AuthorizationCVE-2024-31304 · WordPress plugins & themes · reported by PatchstackHigh 7.1

    Missing Authorization vulnerability in MultiVendorX WC Marketplace.This issue affects WC Marketplace: from n/a through 4.1.3.

    Product
    WC Marketplace
    Affected
    up to 4.1.3
    What to do
    Affects up to 4.1.3. Update WC Marketplace to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Jun 7, 2024WP Stacker: Does not have CSRF check in some placesCVE-2024-5003 · WordPress plugins & themes · reported by WPScanMedium 5.4

    The WP Stacker WordPress plugin through 1.8.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
    WP Stacker
    Affected
    up to 1.8.5
    What to do
    Affects up to 1.8.5. Update WP Stacker to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Jun 6, 2024MultiVendorX Marketplace – WooCommerce MultiVendor Marketplace Solution: Stored Cross-Site ScriptingCVE-2024-5259 · WordPress plugins & themes · reported by WordfenceMedium 6.4

    The MultiVendorX Marketplace – WooCommerce MultiVendor Marketplace Solution plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘hover_animation’ parameter in all versions up to, and including, 4.1.11 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
    MultiVendorX Marketplace – WooCommerce MultiVendor Marketplace Solution
    Affected
    up to 4.1.11
    What to do
    Affects up to 4.1.11. Update MultiVendorX Marketplace – WooCommerce MultiVendor Marketplace Solution to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Jun 3, 2024Search in Place: Missing AuthorizationCVE-2023-26521 · WordPress plugins & themes · reported by PatchstackMedium 4.3

    Missing Authorization vulnerability in CodePeople Search in Place allows Functionality Misuse.This issue affects Search in Place: from n/a through 1.0.104.

    Product
    Search in Place
    Affected
    up to 1.0.104
    What to do
    Affects up to 1.0.104. Update Search in Place 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, 2024GMAce: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')CVE-2023-23872 · WordPress plugins & themes · reported by PatchstackMedium 4.9

    Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in German Mesky GMAce allows Path Traversal.This issue affects GMAce: from n/a through 1.5.2.

    Product
    GMAce
    Affected
    up to 1.5.2
    What to do
    Affects up to 1.5.2. Update GMAce 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, 2024month name translation benaceur: Does not sanitise and escape some of its settingsCVE-2024-3634 · WordPress plugins & themes · reported by WPScanMedium 4.8

    The month name translation benaceur WordPress plugin before 2.3.8 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup)

    Product
    month name translation benaceur
    Fixed in
    2.3.8
    What to do
    Update month name translation benaceur to 2.3.8 or newer.
  • 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 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, 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.
  • 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.

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.