VulnTitan Plugin

Scan WordPress with VulnTitan.

Free plugin for live checks. Pro adds scheduled scans, malware detection, integrity monitoring, alerts and guided remediation.

Free visibility. Pro automation. Download Free Upgrade to Pro
Live Database

Latest vulnerability records

Search by title, slug or version, then narrow the feed by asset type and severity.

34,495 results Updated continuously
  • Plugin Medium Patched: Yes CVSS 4.3/10
    Social Icons Widget & Block <= 4.5.8 - Missing Authorization to Authenticated (Subscriber+) Sharing Configuration Creation

    The Social Icons Widget & Block by WPZOOM plugin for WordPress is vulnerable to unauthorized data modification due to a missing capability check in the add_menu_item() method hooked to admin_menu in all versions up to, and including, 4.5.8. This is due to the method performing wp_insert_post() and update_post_meta() calls to create a sharing configuration without verifying the current user has administrator-level capabilities. This makes it possible for authenticated attackers, with Subscriber-level access and above, to trigger the creation of a published wpzoom-sharing configuration post with default sharing button settings, which causes social sharing buttons to be automatically injected into all post content on the frontend via the the_content filter.

    Published
    Mar 12, 2026
    Affected Product
    Social Icons Widget & Block – Social Media Icons & Share Buttons
    Plugin · social-icons-widget-by-wpzoom
    Affected if you're using
    Versions up to 4.5.8
    Check the full report if you need exact branch-by-branch coverage.
    Patch available
    Yes
    A fixed release is listed for this issue.
    Fixed in
    4.5.9
    Update to this version or a newer safe release.
    What to do

    Update to version 4.5.9, or a newer patched version

    Affected versions
    Versions up to 4.5.8
    Safe / patched versions
    4.5.9
  • Plugin Medium Patched: Yes CVSS 6.4/10
    Calculated Fields Form <= 5.4.5.0 - Authenticated (Contributor+) Stored Cross-Site Scripting via Form Settings

    The Calculated Fields Form plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the form settings in all versions up to, and including, 5.4.5.0. This is due to insufficient capability checks on the form settings save handler and insufficient input sanitization of the `fcontent` field in `fhtml` field types. 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.

    Published
    Mar 12, 2026
    Affected Product
    Calculated Fields Form
    Plugin · calculated-fields-form
    Affected if you're using
    Versions up to 5.4.5.0
    Check the full report if you need exact branch-by-branch coverage.
    Patch available
    Yes
    A fixed release is listed for this issue.
    Fixed in
    5.4.5.1
    Update to this version or a newer safe release.
    What to do

    Update to version 5.4.5.1, or a newer patched version

    Affected versions
    Versions up to 5.4.5.0
    Safe / patched versions
    5.4.5.1
  • Plugin Medium Patched: Yes CVSS 6.4/10
    GetGenie <= 4.3.2 - Insecure Direct Object Reference to Authenticated (Author+) Stored Cross-Site Scripting via REST API

    The GetGenie plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 4.3.2 due to missing validation on a user controlled key in the `action` function. This makes it possible for authenticated attackers, with Author-level access and above, to update post metadata for arbitrary posts. Combined with a lack of input sanitization, this leads to Stored Cross-Site Scripting when a higher-privileged user (such as an Administrator) views the affected post's "Competitor" tab in the GetGenie sidebar.

    Published
    Mar 12, 2026
    Affected Product
    GetGenie – AI Content Writer with Keyword Research & SEO Tracking Tools
    Plugin · getgenie
    Affected if you're using
    Versions up to 4.3.2
    Check the full report if you need exact branch-by-branch coverage.
    Patch available
    Yes
    A fixed release is listed for this issue.
    Fixed in
    4.3.3
    Update to this version or a newer safe release.
    What to do

    Update to version 4.3.3, or a newer patched version

    Affected versions
    Versions up to 4.3.2
    Safe / patched versions
    4.3.3
  • Plugin Medium Patched: Yes CVSS 5.4/10
    GetGenie <= 4.3.2 - Insecure Direct Object Reference to Authenticated (Author+) Arbitrary Post Overwrite/Deletion

    The GetGenie plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 4.3.2. This is due to missing validation on the `id` parameter in the `create()` method of the `GetGenieChat` REST API endpoint. The method accepts a user-controlled post ID and, when a post with that ID exists, calls `wp_update_post()` without verifying that the current user owns the post or that the post is of the expected `getgenie_chat` type. This makes it possible for authenticated attackers, with Author-level access and above, to overwrite arbitrary posts owned by any user — including Administrators — effectively destroying the original content by changing its `post_type` to `getgenie_chat` and reassigning `post_author` to the attacker.

    Published
    Mar 12, 2026
    Affected Product
    GetGenie – AI Content Writer with Keyword Research & SEO Tracking Tools
    Plugin · getgenie
    Affected if you're using
    Versions up to 4.3.2
    Check the full report if you need exact branch-by-branch coverage.
    Patch available
    Yes
    A fixed release is listed for this issue.
    Fixed in
    4.3.3
    Update to this version or a newer safe release.
    What to do

    Update to version 4.3.3, or a newer patched version

    Affected versions
    Versions up to 4.3.2
    Safe / patched versions
    4.3.3
  • Plugin Medium Patched: Yes CVSS 5.3/10
    Formidable Forms <= 6.28 - Unauthenticated Payment Amount Manipulation via 'item_meta' Parameter

    The Formidable Forms plugin for WordPress is vulnerable to an authorization bypass through user-controlled key in all versions up to, and including, 6.28. This is due to the `frm_strp_amount` AJAX handler (`update_intent_ajax`) overwriting the global `$_POST` data with attacker-controlled JSON input and then using those values to recalculate payment amounts via field shortcode resolution in `generate_false_entry()`. The handler relies on a nonce that is publicly exposed in the page's JavaScript (`frm_stripe_vars.nonce`), which provides CSRF protection but not authorization. This makes it possible for unauthenticated attackers to manipulate PaymentIntent amounts before payment completion on forms using dynamic pricing with field shortcodes, effectively paying a reduced amount for goods or services.

    Published
    Mar 12, 2026
    Affected Product
    Formidable Forms – Contact Form Plugin, Survey, Quiz, Payment, Calculator Form & Custom Form Builder
    Plugin · formidable
    Affected if you're using
    Versions up to 6.28
    Check the full report if you need exact branch-by-branch coverage.
    Patch available
    Yes
    A fixed release is listed for this issue.
    Fixed in
    6.29
    Update to this version or a newer safe release.
    What to do

    Update to version 6.29, or a newer patched version

    Affected versions
    Versions up to 6.28
    Safe / patched versions
    6.29
  • Plugin High Patched: Yes CVSS 7.5/10
    Formidable Forms <= 6.28 - Missing Authorization to Unauthenticated Payment Integrity Bypass via PaymentIntent Reuse

    The Formidable Forms plugin for WordPress is vulnerable to a payment integrity bypass in all versions up to, and including, 6.28. This is due to the Stripe Link return handler (`handle_one_time_stripe_link_return_url`) marking payment records as complete based solely on the Stripe PaymentIntent status without comparing the intent's charged amount against the expected payment amount, and the `verify_intent()` function validating only client secret ownership without binding intents to specific forms or actions. This makes it possible for unauthenticated attackers to reuse a PaymentIntent from a completed low-value payment to mark a high-value payment as complete, effectively bypassing payment for goods or services.

    Published
    Mar 12, 2026
    Affected Product
    Formidable Forms – Contact Form Plugin, Survey, Quiz, Payment, Calculator Form & Custom Form Builder
    Plugin · formidable
    Affected if you're using
    Versions up to 6.28
    Check the full report if you need exact branch-by-branch coverage.
    Patch available
    Yes
    A fixed release is listed for this issue.
    Fixed in
    6.29
    Update to this version or a newer safe release.
    What to do

    Update to version 6.29, or a newer patched version

    Affected versions
    Versions up to 6.28
    Safe / patched versions
    6.29
  • Plugin High Patched: Yes CVSS 7.5/10
    Appointment Booking Calendar <= 1.6.9.29 - Missing Authorization to Unauthenticated Sensitive Information Exposure via Settings REST API Endpoint

    The Appointment Booking Calendar — Simply Schedule Appointments plugin for WordPress is vulnerable to unauthorized access of sensitive data in all versions up to and including 1.6.9.29. This is due to two compounding weaknesses: (1) a non-user-bound `public_nonce` is exposed to unauthenticated users through the public `/wp-json/ssa/v1/embed-inner` REST endpoint, and (2) the `get_item()` method in `SSA_Settings_Api` relies on `nonce_permissions_check()` for authorization (which accepts the public nonce) but does not call `remove_unauthorized_settings_for_current_user()` to filter restricted fields. This makes it possible for unauthenticated attackers to access admin-only plugin settings including the administrator email, phone number, internal access tokens, notification configurations, and developer settings via the `/wp-json/ssa/v1/settings/{section}` endpoint. The exposure of appointment tokens also allows an attacker to modify or cancel appointments.

    Published
    Mar 12, 2026
    Affected Product
    Appointment Booking Calendar — Simply Schedule Appointments Booking Plugin
    Plugin · simply-schedule-appointments
    Affected if you're using
    Versions up to 1.6.9.29
    Check the full report if you need exact branch-by-branch coverage.
    Patch available
    Yes
    A fixed release is listed for this issue.
    Fixed in
    1.6.10.0
    Update to this version or a newer safe release.
    What to do

    Update to version 1.6.10.0, or a newer patched version

    Affected versions
    Versions up to 1.6.9.29
    Safe / patched versions
    1.6.10.0
  • Plugin Medium Patched: Yes CVSS 4.3/10
    Appointment Booking Calendar <= 1.6.9.29 - Insecure Direct Object Reference to Authenticated (Staff+) Sensitive Information Exposure

    The Appointment Booking Calendar — Simply Schedule Appointments Booking Plugin plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 1.6.9.29. This is due to the `get_item_permissions_check` method granting access to users with the `ssa_manage_appointments` capability without validating staff ownership of the requested appointment. This makes it possible for authenticated attackers, with custom-level access and above (users granted the ssa_manage_appointments capability, such as Team Members), to view appointment records belonging to other staff members and access sensitive customer personally identifiable information via the appointment ID parameter.

    Published
    Mar 12, 2026
    Affected Product
    Appointment Booking Calendar — Simply Schedule Appointments Booking Plugin
    Plugin · simply-schedule-appointments
    Affected if you're using
    Versions up to 1.6.9.29
    Check the full report if you need exact branch-by-branch coverage.
    Patch available
    Yes
    A fixed release is listed for this issue.
    Fixed in
    1.6.10.0
    Update to this version or a newer safe release.
    What to do

    Update to version 1.6.10.0, or a newer patched version

    Affected versions
    Versions up to 1.6.9.29
    Safe / patched versions
    1.6.10.0
  • Plugin Critical Patched: Yes CVSS 9.8/10
    Pix for WooCommerce <= 1.5.0 - Unauthenticated Arbitrary File Upload

    The Pix for WooCommerce plugin for WordPress is vulnerable to arbitrary file uploads due to missing capability check and missing file type validation in the 'lkn_pix_for_woocommerce_c6_save_settings' function in all versions up to, and including, 1.5.0. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible.

    Published
    Mar 12, 2026
    Affected Product
    Pix for WooCommerce
    Plugin · payment-gateway-pix-for-woocommerce
    Affected if you're using
    Versions up to 1.5.0
    Check the full report if you need exact branch-by-branch coverage.
    Patch available
    Yes
    A fixed release is listed for this issue.
    Fixed in
    1.6.0
    Update to this version or a newer safe release.
    What to do

    Update to version 1.6.0, or a newer patched version

    Affected versions
    Versions up to 1.5.0
    Safe / patched versions
    1.6.0
  • Plugin Medium Patched: Yes CVSS 6.1/10
    Simple Ajax Chat <= 20260217 - Unauthenticated Stored Cross-Site Scripting via 'c'

    The Simple Ajax Chat plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'c' parameter in versions up to, and including, 20260217 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

    Published
    Mar 12, 2026
    Affected Product
    Simple Ajax Chat – Add a Fast, Secure Chat Box
    Plugin · simple-ajax-chat
    Affected if you're using
    Versions up to 20260217
    Check the full report if you need exact branch-by-branch coverage.
    Patch available
    Yes
    A fixed release is listed for this issue.
    Fixed in
    20260301
    Update to this version or a newer safe release.
    What to do

    Update to version 20260301, or a newer patched version

    Affected versions
    Versions up to 20260217
    Safe / patched versions
    20260301