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

4,219 results · page 5 of 85

  • Jun 2, 2026Remove NoFollow Commenter URL: Cross-Site Request ForgeryCVE-2026-9730 · WordPress plugins & themes · reported by WordfenceMedium 4.3

    The Remove NoFollow Commenter URL plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0. This is due to missing or incorrect nonce validation on the gmz_comment_settings_save function. This makes it possible for unauthenticated attackers to modify the plugin's comment-display setting via a forged request via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

    Product
    Remove NoFollow Commenter URL
    Affected
    up to 1.0
    What to do
    Affects up to 1.0. Update Remove NoFollow Commenter URL to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Jun 2, 2026Google Plus One Bottom: Cross-Site Request ForgeryCVE-2026-9723 · WordPress plugins & themes · reported by WordfenceMedium 4.3

    The Google Plus One Bottom plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 0.0.2. This is due to missing or incorrect nonce validation on the googlePlusOneAdmin function. This makes it possible for unauthenticated attackers to modify the plugin's settings, including the plusone-lang, plusone-callback, and plusone-url options stored in the database via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

    Product
    Google Plus One Bottom
    Affected
    up to 0.0.2
    What to do
    Affects up to 0.0.2. Update Google Plus One Bottom to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Jun 2, 2026Laiser Tag: Cross-Site Request ForgeryCVE-2026-9722 · WordPress plugins & themes · reported by WordfenceMedium 4.3

    The Laiser Tag plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.2.5. This is due to missing or incorrect nonce validation on the addOptionsPageFields function. This makes it possible for unauthenticated attackers to update the plugin's settings, including the API key, tag blacklist, relevance threshold, batch size, and tagging toggles, via a forged request via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

    Product
    Laiser Tag
    Affected
    up to 1.2.5
    What to do
    Affects up to 1.2.5. Update Laiser Tag to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Jun 2, 2026Tectite Forms: Cross-Site Request ForgeryCVE-2026-9599 · WordPress plugins & themes · reported by WordfenceMedium 4.3

    The Tectite Forms plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.3. This is due to missing or incorrect nonce validation on the admin_init function. This makes it possible for unauthenticated attackers to modify the plugin's settings, including the tectite_forms_button option, via a forged request via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

    Product
    Tectite Forms
    Affected
    up to 1.3
    What to do
    Affects up to 1.3. Update Tectite Forms to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Jun 2, 2026Remove meta boxes per user role: Cross-Site Request ForgeryCVE-2026-8422 · WordPress plugins & themes · reported by WordfenceMedium 4.3

    The Remove meta boxes per user role plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.01. This is due to missing or incorrect nonce validation on the 'remove-meta-boxes-per-user-role' page. This makes it possible for unauthenticated attackers to modify or reset the plugin's per-role meta box visibility settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

    Product
    Remove meta boxes per user role
    Affected
    up to 1.01
    What to do
    Affects up to 1.01. Update Remove meta boxes per user role to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Jun 2, 2026BirdSeed: Cross-Site Request ForgeryCVE-2026-4071 · WordPress plugins & themes · reported by WordfenceMedium 4.3

    The BirdSeed plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.2.0. This is due to missing nonce validation in the birdseed_plugin_settings_page() function. The function processes the 'birdseed_token' GET parameter and saves it to the database via update_option() without verifying a nonce. This makes it possible for unauthenticated attackers to change the plugin's BirdSeed token setting via a forged request, granted they can trick a site administrator into performing an action such as clicking a link.

    Product
    BirdSeed
    Affected
    up to 2.2.0
    What to do
    Affects up to 2.2.0. Update BirdSeed to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 29, 2026Media Library Assistant: Cross-Site Request ForgeryCVE-2026-6075 · WordPress plugins & themes · reported by WordfenceHigh 8.1

    The Media Library Assistant plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.35 This is due to missing nonce verification on the bulk action handlers in the settings tab handlers. This makes it possible for unauthenticated attackers to trick an administrator into performing bulk delete, edit, or purge operations on plugin settings and attachment metadata via a forged request.

    Product
    Media Library Assistant
    Affected
    up to 3.35
    What to do
    Affects up to 3.35. Update Media Library Assistant to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 28, 2026PeachPay — Payments & Express Checkout for WooCommerce (supports Stripe, PayPal, Square, Authorize.net, NMI): Cross-Site Request ForgeryCVE-2026-9618 · WordPress plugins & themes · reported by WordfenceMedium 4.3

    The PeachPay — Payments & Express Checkout for WooCommerce (supports Stripe, PayPal, Square, Authorize.net, NMI) plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.120.46. This is due to missing or incorrect nonce validation on the peachpay_stripe_handle_admin_actions function. This makes it possible for unauthenticated attackers to permanently delete all stored Stripe credentials — including publishable keys, secret keys, webhook secrets, and Apple Pay configuration — from the WordPress database, disabling Stripe payment processing for the store via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

    Product
    PeachPay — Payments & Express Checkout for WooCommerce (supports Stripe, PayPal, Square, Authorize.net, NMI)
    Affected
    up to 1.120.46
    What to do
    Affects up to 1.120.46. Update PeachPay — Payments & Express Checkout for WooCommerce (supports Stripe, PayPal, Square, Authorize.net, NMI) to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 28, 2026WP Contact Form 7 DB Handler: Cross-Site Request Forgery leading to Arbitrary File DeletionCVE-2026-6455 · WordPress plugins & themes · reported by WordfenceHigh 8.1

    The WP Contact Form 7 DB Handler plugin for WordPress is vulnerable to Cross-Site Request Forgery leading to Arbitrary File Deletion via SQL Injection and PHP Object Injection in versions up to and including 3.0. This is due to a missing nonce verification in the process_bulk_action() function, the nonce check is only executed when _wpnonce is present in the POST body, allowing it to be trivially bypassed by omitting the field, combined with the use of an unsanitized, unparameterized user-supplied value in a numeric SQL context (WHERE ID = $ID) and the unsafe deserialization of the query result's post_content field. An attacker can craft a CSRF page that tricks a logged-in administrator into triggering a UNION-based SQL injection payload (using CHAR() to avoid esc_sql quote-escaping) that returns a malicious serialized PHP array as post_content; upon deserialization, array values associated with keys containing 'ys_cfdbh_file' are used as file paths appended to the uploads directory path without any path traversal validation, and then passed to wp_delete_file(), allowing the attacker to delete arbitrary files on the server (e.g., wp-config.php, system files).

    Product
    WP Contact Form 7 DB Handler
    Affected
    up to 3.0
    What to do
    Affects up to 3.0. Update WP Contact Form 7 DB Handler to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 28, 2026Easy Digital Downloads: Cross-Site Request ForgeryCVE-2026-7533 · WordPress plugins & themes · reported by WordfenceMedium 4.3

    The Easy Digital Downloads plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.6.7. This is due to missing nonce verification in the `handle_oauth_redirect()` function, which is registered on the `admin_init` hook and processes Square OAuth tokens from a user-supplied GET parameter without any CSRF token validation. This makes it possible for unauthenticated attackers to overwrite the store's Square payment gateway credentials by tricking a logged-in administrator into clicking a crafted link, potentially resulting in payment account hijacking.

    Product
    Easy Digital Downloads
    Affected
    up to 3.6.7
    What to do
    Affects up to 3.6.7. Update Easy Digital Downloads to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 28, 2026Independent Analytics: Server-Side Request ForgeryCVE-2026-5737 · WordPress plugins & themes · reported by WordfenceMedium 6.5

    The Independent Analytics plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 2.14.9. This is due to a public tracking route at /wp-json/iawp/search that accepts attacker-controlled referrer_url values when the signature matches, combined with a scheduled favicon fetcher that performs unrestricted cURL requests to stored domains. The signature validation is insufficient because the signature is embedded in publicly-accessible JavaScript and the salt is static per site, allowing attackers to extract valid signatures. The favicon downloader uses raw cURL functions without any SSRF protection mechanisms (no localhost blocking, no private network filtering, and does not use WordPress's wp_safe_remote_* functions). This makes it possible for unauthenticated attackers to inject malicious referrer domains into the database and trigger server-side requests to arbitrary hosts including internal services.

    Product
    Independent Analytics
    Affected
    up to 2.14.9
    What to do
    Affects up to 2.14.9. Update Independent Analytics to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 27, 2026MetaMagic SEO: Cross-Site Request ForgeryCVE-2026-8942 · WordPress plugins & themes · reported by WordfenceMedium 4.3

    The MetaMagic SEO Plugin plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.6. This is due to missing or incorrect nonce validation on the metamagic_update_options function. This makes it possible for unauthenticated attackers to modify the plugin's SEO settings, including enabling or disabling the plugin and toggling description and keyword meta tag output via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

    Product
    MetaMagic SEO
    Affected
    up to 1.6
    What to do
    Affects up to 1.6. Update MetaMagic SEO to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 27, 2026WP Promoter: Cross-Site Request ForgeryCVE-2026-8906 · WordPress plugins & themes · reported by WordfenceMedium 6.1

    The WP Promoter plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.3. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

    Product
    WP Promoter
    Affected
    up to 1.3
    What to do
    Affects up to 1.3. Update WP Promoter to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 27, 2026GoStats for: Cross-Site Request ForgeryCVE-2026-8943 · WordPress plugins & themes · reported by WordfenceMedium 4.3

    The GoStats for WordPress plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.4. This is due to missing or incorrect nonce validation on the gostats_manage() function. This makes it possible for unauthenticated attackers to update the plugin's settings (gostats_siteid and gostats_server options) via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

    Product
    GoStats for
    Affected
    up to 1.4
    What to do
    Affects up to 1.4. Update GoStats for to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 27, 2026CDN Linker lite: Cross-Site Request ForgeryCVE-2026-8941 · WordPress plugins & themes · reported by WordfenceMedium 4.3

    The CDN Linker lite plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.3.1. This is due to missing or incorrect nonce validation on the ossdl_off_options() function. This makes it possible for unauthenticated attackers to update the plugin's settings — including the CDN URL used to rewrite all static asset references on the site — via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

    Product
    CDN Linker lite
    Affected
    up to 1.3.1
    What to do
    Affects up to 1.3.1. Update CDN Linker lite to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 27, 2026Search Simple Fields: Cross-Site Request ForgeryCVE-2026-8939 · WordPress plugins & themes · reported by WordfenceMedium 4.3

    The Search Simple Fields plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 0.2. This is due to missing or incorrect nonce validation on the search_simple_fields_options() function in functions_admin.php. This makes it possible for unauthenticated attackers to modify the plugin's settings — including post types to search in, custom fields, media fields and the custom media function name — via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

    Product
    Search Simple Fields
    Affected
    up to 0.2
    What to do
    Affects up to 0.2. Update Search Simple Fields to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 27, 2026auto making JSON-LD: Cross-Site Request ForgeryCVE-2026-8938 · WordPress plugins & themes · reported by WordfenceMedium 4.3

    The auto making JSON-LD plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 4.5.3. This is due to missing or incorrect nonce validation on the amJL_certification function. This makes it possible for unauthenticated attackers to update the plugin's license key option, and subsequently trigger license validation and pro feature installation on the victim site without the administrator's consent via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. Successful exploitation can trigger downstream calls to amJL_is_license_valid() and amJL_download_and_install_pro_features(), meaning the impact extends beyond a simple settings change to unauthorized installation of plugin components.

    Product
    auto making JSON-LD
    Affected
    up to 4.5.3
    What to do
    Affects up to 4.5.3. Update auto making JSON-LD to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 27, 2026WP AutoBuzz: Cross-Site Request ForgeryCVE-2026-8911 · WordPress plugins & themes · reported by WordfenceMedium 6.1

    The WP AutoBuzz plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.1.1. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. This vulnerability bypasses WordPress's DISALLOW_UNFILTERED_HTML protection because the unsanitized value is written directly via update_option at the plugin level, entirely outside of WordPress post content handling.

    Product
    WP AutoBuzz
    Affected
    up to 1.1.1
    What to do
    Affects up to 1.1.1. Update WP AutoBuzz to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 27, 2026Two-factor authentication (formerly IP Vault): Cross-Site Request ForgeryCVE-2026-8903 · WordPress plugins & themes · reported by WordfenceMedium 4.3

    The Two-factor authentication (formerly IP Vault) plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.1. This is due to missing or incorrect nonce validation on the ipv_save_changes function. This makes it possible for unauthenticated attackers to modify the plugin's firewall and two-factor authentication settings — including the operating mode, request include/exclude rules, authentication slug, and log retention period — potentially disabling protection entirely via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

    Product
    Two-factor authentication (formerly IP Vault)
    Affected
    up to 2.1
    What to do
    Affects up to 2.1. Update Two-factor authentication (formerly IP Vault) to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 27, 2026Genzel breadcrumbs: Cross-Site Request ForgeryCVE-2026-8708 · WordPress plugins & themes · reported by WordfenceMedium 4.3

    The Genzel breadcrumbs plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.2. This is due to missing or incorrect nonce validation on the _options_page function. This makes it possible for unauthenticated attackers to update the plugin's breadcrumb configuration, including templates, delimiter, home label, home URI, and breadcrumb rules via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

    Product
    Genzel breadcrumbs
    Affected
    up to 1.2
    What to do
    Affects up to 1.2. Update Genzel breadcrumbs to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 27, 2026Old Posts Highlighter: Cross-Site Request ForgeryCVE-2026-7614 · WordPress plugins & themes · reported by WordfenceMedium 4.3

    The Old Posts Highlighter plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.3. This is due to missing or incorrect nonce validation on the OPH_options function. This makes it possible for unauthenticated attackers to update the plugin's configuration settings without authorization via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

    Product
    Old Posts Highlighter
    Affected
    up to 1.0.3
    What to do
    Affects up to 1.0.3. Update Old Posts Highlighter to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 27, 2026CM Ad Changer – A simple tool to control and optimize your site's banners: Cross-Site Request ForgeryCVE-2026-9236 · WordPress plugins & themes · reported by WordfenceMedium 4.3

    The CM Ad Changer – A simple tool to control and optimize your site's banners plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.0.7. This is due to missing or incorrect nonce validation on the cmac_campaigns_action function. This makes it possible for unauthenticated attackers to permanently delete arbitrary advertising campaigns, including their associated banner records and uploaded files via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

    Product
    CM Ad Changer – A simple tool to control and optimize your site's banners
    Affected
    up to 2.0.7
    What to do
    Affects up to 2.0.7. Update CM Ad Changer – A simple tool to control and optimize your site's banners to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 26, 2026Zohocorp Zoho Mail wordpress plugin is vulnerable to Cross-Site request forgery (CSRF).CVE-2026-8174 · WordPress plugins & themes · reported by 0fc0942c-577d-436f-ae8e-945763c79b02Medium 5.7

    Zohocorp Zoho Mail wordpress plugin is vulnerable to Cross-Site request forgery (CSRF). This issue affects Zoho Mail wordpress plugin versions before 1.6.2.

    Fixed in
    1.6.2
    What to do
    Update the plugin to 1.6.2 or newer.
  • May 25, 2026CformsII: Cross-Site Request Forgery (CSRF)CVE-2026-39436 · WordPress plugins & themes · reported by PatchstackHigh 7.1

    Cross-Site Request Forgery (CSRF) vulnerability in bgermann CformsII allows Cross Site Request Forgery. This issue affects CformsII: from n/a through 15.1.3.

    Product
    CformsII
    Affected
    up to 15.1.3
    What to do
    Affects up to 15.1.3. Update CformsII to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 25, 2026WPSubscription: Cross-Site Request Forgery (CSRF)CVE-2026-24554 · WordPress plugins & themes · reported by PatchstackMedium 4.3

    Cross-Site Request Forgery (CSRF) vulnerability in Convers Lab WPSubscription allows Cross Site Request Forgery. This issue affects WPSubscription: from n/a through 1.9.1.

    Product
    WPSubscription
    Affected
    up to 1.9.1
    What to do
    Affects up to 1.9.1. Update WPSubscription to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 25, 2026Organization chart: Cross-Site Request Forgery (CSRF)CVE-2026-24597 · WordPress plugins & themes · reported by PatchstackMedium 4.3

    Cross-Site Request Forgery (CSRF) vulnerability in WpDevArt Organization chart allows Cross Site Request Forgery. This issue affects Organization chart: from n/a through 1.7.5.

    Product
    Organization chart
    Affected
    up to 1.7.5
    What to do
    Affects up to 1.7.5. Update Organization chart to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 25, 2026Export WP Page to Static HTML/CSS: Cross-Site Request Forgery (CSRF)CVE-2026-24574 · WordPress plugins & themes · reported by PatchstackMedium 6.5

    Cross-Site Request Forgery (CSRF) vulnerability in Recorp Export WP Page to Static HTML/CSS allows Cross Site Request Forgery. This issue affects Export WP Page to Static HTML/CSS: from n/a through 6.0.0.

    Product
    Export WP Page to Static HTML/CSS
    Affected
    up to 6.0.0
    What to do
    Affects up to 6.0.0. Update Export WP Page to Static HTML/CSS to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 22, 2026FluentCRM – Email Newsletter, Automation, Email Marketing, Email Campaigns, Optins, Leads, and CRM Solution: Blind Server-Side Request ForgeryCVE-2026-7798 · WordPress plugins & themes · reported by WordfenceMedium 5.4

    The FluentCRM – Email Newsletter, Automation, Email Marketing, Email Campaigns, Optins, Leads, and CRM Solution plugin for WordPress is vulnerable to Blind Server-Side Request Forgery in all versions up to, and including, 2.9.87 via the 'SubscribeURL' parameter. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services. Exploitation requires that the SES bounce handling key ('_fc_bounce_key') has never been stored (i.e., the site is in its default/unconfigured state with respect to SES bounce handling) as visiting the bounce configuration page auto-generates and stores a random key that causes the authentication check to evaluate correctly and reject unauthenticated requests.

    Product
    FluentCRM – Email Newsletter, Automation, Email Marketing, Email Campaigns, Optins, Leads, and CRM Solution
    Affected
    up to 2.9.87
    What to do
    Affects up to 2.9.87. Update FluentCRM – Email Newsletter, Automation, Email Marketing, Email Campaigns, Optins, Leads, and CRM Solution to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 22, 2026Widget Context: Cross-Site Request ForgeryCVE-2026-7615 · WordPress plugins & themes · reported by WordfenceMedium 4.3

    The Widget Context plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.3.3. This is due to missing or incorrect nonce validation on the save_widget_context_settings function. This makes it possible for unauthenticated attackers to modify widget visibility context settings stored in the WordPress options table via a forged POST request to /wp-admin/widgets.php via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

    Product
    Widget Context
    Affected
    up to 1.3.3
    What to do
    Affects up to 1.3.3. Update Widget Context to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 22, 2026Alfie – Feed: Cross-Site Request ForgeryCVE-2026-4070 · WordPress plugins & themes · reported by WordfenceMedium 4.3

    The Alfie – Feed Plugin plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.2.1. This is due to missing nonce validation on the alfie_manage() function which handles feed deletion via the 'delete' GET parameter. This makes it possible for unauthenticated attackers to delete arbitrary plugin feed data (from alfie_colindex, alfie_producten, alfie_reactions, and alfie_searchproduct tables) via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

    Product
    Alfie – Feed
    Affected
    up to 1.2.1
    What to do
    Affects up to 1.2.1. Update Alfie – Feed to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 20, 2026Anomify AI – Anomaly Detection and Alerting: Cross-Site Request Forgery (CSRF) leading to Stored Cross-Site Scripting (XSS)CVE-2026-6405 · WordPress plugins & themes · reported by WordfenceMedium 4.3

    The Anomify AI – Anomaly Detection and Alerting plugin for WordPress is vulnerable to Cross-Site Request Forgery (CSRF) leading to Stored Cross-Site Scripting (XSS) in versions up to and including 0.3.6. This is due to missing nonce verification on the settings page handler and insufficient output escaping in the admin_options.php template. The settings form includes no wp_nonce_field() and the handler performs no check_admin_referer() check, meaning any cross-origin POST can modify plugin settings. The API key field is sanitized only with sanitize_text_field(), which strips HTML tags but does not encode double-quote characters; the value is then rendered into an HTML attribute via bare echo without esc_attr(), allowing a double-quote attribute-escape payload to survive both sanitization and storage. This makes it possible for unauthenticated attackers to inject arbitrary web scripts by tricking a logged-in administrator into visiting a malicious page that submits a forged request, storing the payload in the database and causing it to execute in the administrator's browser whenever the plugin settings page is visited.

    Product
    Anomify AI – Anomaly Detection and Alerting
    Affected
    up to 0.3.6
    What to do
    Affects up to 0.3.6. Update Anomify AI – Anomaly Detection and Alerting to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 19, 2026Remove Yellow BGBOX: Cross-Site Request ForgeryCVE-2026-8424 · WordPress plugins & themes · reported by WordfenceMedium 4.3

    The Remove Yellow BGBOX plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0. This is due to missing or incorrect nonce validation on the 'rybb_api_settings' page. This makes it possible for unauthenticated attackers to reset the plugin's stored settings by overwriting its configuration via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

    Product
    Remove Yellow BGBOX
    Affected
    up to 1.0
    What to do
    Affects up to 1.0. Update Remove Yellow BGBOX to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 19, 2026JaviBola Custom Theme Test: Cross-Site Request ForgeryCVE-2026-8423 · WordPress plugins & themes · reported by WordfenceMedium 4.3

    The JaviBola Custom Theme Test plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.0.5. This is due to missing or incorrect nonce validation on the options page. This makes it possible for unauthenticated attackers to change the site's active theme by modifying the jbct_theme option via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

    Product
    JaviBola Custom Theme Test
    Affected
    up to 2.0.5
    What to do
    Affects up to 2.0.5. Update JaviBola Custom Theme Test to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 19, 2026BLOGCHAT Chat System: Cross-Site Request ForgeryCVE-2026-8420 · WordPress plugins & themes · reported by WordfenceMedium 6.1

    The BLOGCHAT Chat System plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.3.6.3. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

    Product
    BLOGCHAT Chat System
    Affected
    up to 1.3.6.3
    What to do
    Affects up to 1.3.6.3. Update BLOGCHAT Chat System to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 19, 2026Amazon Scraper: Cross-Site Request ForgeryCVE-2026-8419 · WordPress plugins & themes · reported by WordfenceMedium 4.3

    The Amazon Scraper plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.1. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

    Product
    Amazon Scraper
    Affected
    up to 1.1
    What to do
    Affects up to 1.1. Update Amazon Scraper to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 19, 2026Games Catalog: Cross-Site Request ForgeryCVE-2026-8418 · WordPress plugins & themes · reported by WordfenceMedium 4.3

    The Games Catalog plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.2.0. This is due to missing or incorrect nonce validation on the gc_crud() function which handles the delete action (action=delete) via a GET request without any wp_verify_nonce() / check_admin_referer() call. This makes it possible for unauthenticated attackers to delete arbitrary game catalog entries (including the associated WordPress post created for the game) via a forged request, granted they can trick a site administrator into performing an action such as clicking on a link.

    Product
    Games Catalog
    Affected
    up to 1.2.0
    What to do
    Affects up to 1.2.0. Update Games Catalog to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 19, 2026Bigfishgames Syndicate: Cross-Site Request ForgeryCVE-2026-6452 · WordPress plugins & themes · reported by WordfenceMedium 4.3

    The Bigfishgames Syndicate plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.2. This is due to missing or incorrect nonce validation on the bigfishgames_syndicate_submenu() function. This makes it possible for unauthenticated attackers to reset plugin settings and update them via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

    Product
    Bigfishgames Syndicate
    Affected
    up to 1.2
    What to do
    Affects up to 1.2. Update Bigfishgames Syndicate to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 19, 2026Bottom Bar: Cross-Site Request ForgeryCVE-2026-6401 · WordPress plugins & themes · reported by WordfenceMedium 4.3

    The Bottom Bar plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to and including 0.1.7. This is due to missing nonce verification on the plugin's settings update forms handled in bottom-bar-admin.php. None of the three settings forms (main settings, sharing services, restore defaults) include a wp_nonce_field(), and the server-side processing code never calls check_admin_referer() or any equivalent nonce validation before processing POST data and calling update_option(). This makes it possible for unauthenticated attackers to trick a logged-in administrator into submitting a crafted request that updates plugin configuration options, such as changing the language, maximum post counts, or enabled sharing services.

    Product
    Bottom Bar
    Affected
    up to 0.1.7
    What to do
    Affects up to 0.1.7. Update Bottom Bar to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 19, 2026Child Height Predictor by Ostheimer: Cross-Site Request ForgeryCVE-2026-6400 · WordPress plugins & themes · reported by WordfenceMedium 4.3

    The Child Height Predictor by Ostheimer plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to and including 1.3. This is due to missing nonce verification in the options() function, which handles plugin settings updates. The form template does not include a wp_nonce_field() call, and the handler never calls check_admin_referer() or wp_verify_nonce(). This makes it possible for unauthenticated attackers to trick a site administrator into clicking a link or visiting a malicious page that submits a forged POST request, causing unauthorized changes to the plugin settings such as unit preferences to be persisted to the database via update_option().

    Product
    Child Height Predictor by Ostheimer
    Affected
    up to 1.3
    What to do
    Affects up to 1.3. Update Child Height Predictor by Ostheimer to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 19, 2026Word 2 Cash: Cross-Site Request Forgery leading to Stored Cross-Site ScriptingCVE-2026-6395 · WordPress plugins & themes · reported by WordfenceMedium 6.1

    The Word 2 Cash plugin for WordPress is vulnerable to Cross-Site Request Forgery leading to Stored Cross-Site Scripting in versions up to and including 0.9.2. This is due to the complete absence of nonce verification on the settings save handler in the w2c_admin() function, combined with missing input sanitization before storage and missing output escaping when rendering the stored value. The w2c-definitions POST parameter is saved raw via update_option() and later echoed without escaping inside a <textarea> element. This makes it possible for unauthenticated attackers to forge a request on behalf of a logged-in administrator, storing arbitrary JavaScript payloads that execute in the WordPress admin panel whenever the settings page is visited.

    Product
    Word 2 Cash
    Affected
    up to 0.9.2
    What to do
    Affects up to 0.9.2. Update Word 2 Cash to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 19, 2026Nexa Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE: Server-Side Request Forgery (SSRF)CVE-2026-6394 · WordPress plugins & themes · reported by WordfenceMedium 5.4

    The Nexa Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE plugin for WordPress is vulnerable to Server-Side Request Forgery (SSRF) in versions up to and including 1.1.1. This is due to the import_demo() function accepting a user-supplied URL in the demo_json_file POST parameter and passing it directly to wp_remote_get() without any URL validation or restriction against internal or private network destinations. The nexa_blocks_nonce required for the AJAX action is publicly exposed in the HTML source of any frontend page where the plugin is active via wp_localize_script on the enqueue_block_assets hook, effectively making the nonce available to all visitors and bypassing any intended authentication barrier. This makes it possible for unauthenticated attackers to make server-side HTTP requests to arbitrary internal or external destinations, potentially exposing internal services, cloud metadata endpoints such as the AWS instance metadata service, localhost services, and other resources not intended to be publicly accessible. A secondary SSRF vector also exists whereby image URLs extracted from the attacker-controlled JSON response are subsequently fetched via a secon

    Product
    Nexa Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE
    Affected
    up to 1.1.1
    What to do
    Affects up to 1.1.1. Update Nexa Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 19, 2026Sentence To SEO (keywords, description and tags): Cross-Site Request ForgeryCVE-2026-6391 · WordPress plugins & themes · reported by WordfenceMedium 6.1

    The Sentence To SEO (keywords, description and tags) plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0. This is due to missing or incorrect nonce validation on the create_admin_page() function. This makes it possible for unauthenticated attackers to inject malicious web scripts and update plugin settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

    Product
    Sentence To SEO (keywords, description and tags)
    Affected
    up to 1.0
    What to do
    Affects up to 1.0. Update Sentence To SEO (keywords, description and tags) to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 15, 2026Notify Odoo: Cross-Site Request ForgeryCVE-2026-8425 · WordPress plugins & themes · reported by WordfenceMedium 4.3

    The Notify Odoo plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.1. This is due to missing or incorrect nonce validation on the _updateSettings function. This makes it possible for unauthenticated attackers to change the Notify Odoo URL to an attacker-controlled URL and modify notification, tracking image, and allowed IP address settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

    Product
    Notify Odoo
    Affected
    up to 1.0.1
    What to do
    Affects up to 1.0.1. Update Notify Odoo to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 14, 2026LatePoint: Cross-Site Request ForgeryCVE-2026-5365 · WordPress plugins & themes · reported by WordfenceMedium 4.3

    The LatePoint plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to and including 5.3.2. This is due to missing nonce verification on the request_cancellation() function. This makes it possible for unauthenticated attackers to cancel a logged-in customer's bookings via a forged request, granted they can trick the customer into performing an action such as clicking on a link.

    Product
    LatePoint
    Affected
    up to 5.3.2
    What to do
    Affects up to 5.3.2. Update LatePoint to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 12, 2026Zawgyi Embed: Cross-Site Request ForgeryCVE-2026-7616 · WordPress plugins & themes · reported by WordfenceMedium 4.3

    The Zawgyi Embed plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.1.1. This is due to missing or incorrect nonce validation on the zawgyi_adminpage function. This makes it possible for unauthenticated attackers to update the plugin's zawgyi_forceCSS setting by submitting a forged POST request to options-general.php?page=zawgyi_embed via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

    Product
    Zawgyi Embed
    Affected
    up to 2.1.1
    What to do
    Affects up to 2.1.1. Update Zawgyi Embed to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 12, 2026WP-Redirection: Cross-Site Request ForgeryCVE-2026-7562 · WordPress plugins & themes · reported by WordfenceMedium 4.3

    The WP-Redirection plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to and including 1.0.3. This is due to the absence of a nonce field in the admin settings form and the lack of any nonce verification (via check_admin_referer() or wp_verify_nonce()) in the displayWPRedirectionManagementPage() function before processing POST requests that add, edit, or delete URL redirection rules. This makes it possible for unauthenticated attackers to trick a logged-in administrator into clicking a crafted link, causing the attacker to create, modify, or delete redirection records in the plugin's database table without the administrator's consent.

    Product
    WP-Redirection
    Affected
    up to 1.0.3
    What to do
    Affects up to 1.0.3. Update WP-Redirection to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 12, 2026Tm – WordPress Redirection: Cross-Site Request ForgeryCVE-2026-7561 · WordPress plugins & themes · reported by WordfenceMedium 6.1

    The Tm – WordPress Redirection plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.2. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

    Product
    Tm – WordPress Redirection
    Affected
    up to 1.2
    What to do
    Affects up to 1.2. Update Tm – WordPress Redirection to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 12, 2026Woo Commerce Minimum Weight: Cross-Site Request ForgeryCVE-2026-6932 · WordPress plugins & themes · reported by WordfenceMedium 4.3

    The Woo Commerce Minimum Weight plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to and including 3.0.1. This is due to missing nonce verification on the settings update handler in edit-weight.php. This makes it possible for unauthenticated attackers to modify the minimum order weight setting by tricking a site administrator into clicking a link or visiting an attacker-controlled page containing a forged POST request.

    Product
    Woo Commerce Minimum Weight
    Affected
    up to 3.0.1
    What to do
    Affects up to 3.0.1. Update Woo Commerce Minimum Weight to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 12, 2026Skysa Text Ticker App: Cross-Site Request ForgeryCVE-2026-6710 · WordPress plugins & themes · reported by WordfenceMedium 4.3

    The Skysa Text Ticker App plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.4. This is due to missing or incorrect nonce validation on the SkysaApps_Admin_AppPage function. This makes it possible for unauthenticated attackers to trick a site administrator into making a forged request to modify the plugin's settings, including the scrolling message text and URL, via a forged cross-site request via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

    Product
    Skysa Text Ticker App
    Affected
    up to 1.4
    What to do
    Affects up to 1.4. Update Skysa Text Ticker App to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 10, 2026WordPress Plugin Curtain 1.0.2 contains a cross-site request forgery vulnerability that allows attackers to activate or deactivate site maintenance mode by crafCVE-2022-50955 · WordPress plugins & themes · reported by VulnCheckMedium 5.3

    WordPress Plugin Curtain 1.0.2 contains a cross-site request forgery vulnerability that allows attackers to activate or deactivate site maintenance mode by crafting malicious requests. Attackers can trick authenticated administrators into submitting forged requests to the options-general.php page with curtain parameters to toggle maintenance mode without valid nonce validation.

    What to do
    Update the plugin to the newest version.

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.