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.

36,430 results Updated continuously

Records stay compact by default so the feed is easier to scan. Expand any advisory when you need remediation and full version coverage.

  • Plugin High Patched: Yes CVSS 7.5/10
    GEO my WP <= 4.5.5 - Unauthenticated SQL Injection via 'swlatlng' / 'nelatlng' Parameters

    The GEO my WP plugin for WordPress is vulnerable to SQL Injection via the 'swlatlng' and 'nelatlng' parameters in all versions up to, and including, 4.5.5 The parameters are read from $_SERVER['QUERY_STRING'] via parse_str() (bypassing WordPress's wp_magic_quotes protection, which only covers $_POST/$_GET/$_COOKIE/$_REQUEST), then each is split on ',' via explode() and the resulting fragments are interpolated directly into a SQL BETWEEN clause in gmw_get_locations_within_boundaries_sql() without is_numeric() validation, (float) casting, esc_sql(), or $wpdb->prepare(). This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. Exploitation requires the site to host the Posts Locator search-results shortcode (`[gmw form="results" form_id=N]`) on a public page and to have at least one published post with an associated gmw_location row.

    Published
    May 29, 2026
    Affected Product
    GEO my WP
    Plugin · geo-my-wp
    Affected window
    Versions up to 4.5.5
    Expand for exact coverage and remediation detail.
    Patch status
    Patched release available
    Fixed in 4.5.5.1
    Recommended next step
    Update to 4.5.5.1
    Move to a safe release and validate after update.
    Detailed remediation and version lists stay hidden until expanded.
    Affected if you're using
    Versions up to 4.5.5
    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.5.1
    Update to this version or a newer safe release.
    What to do

    Update to version 4.5.5.1, or a newer patched version

    Affected versions
    Versions up to 4.5.5
    Safe / patched versions
    4.5.5.1
  • Plugin High Patched: Yes CVSS 7.5/10
    Simple History – Track, Log, and Audit WordPress Changes <= 5.26.0 - Authenticated (Subscriber+) Account Takeover via Missing Authorization on Event Reaction Endpoint

    The Simple History – Track, Log, and Audit WordPress Changes plugin for WordPress is vulnerable to authenticated (Subscriber+) account takeover in all versions up to, and including, 5.26.0 via the event reaction endpoints (react_to_event() / unreact_to_event()). The endpoints register get_items_permissions_check() as their permission_callback, which only verifies the requester is logged in and does not enforce the per-logger capability checks normally applied by Log_Query. As a result, a Subscriber-level user can POST to /wp-json/simple-history/v1/events//react with the _fields=context query parameter and read the full context of any Simple History event — including SimpleUserLogger entries that record the full password-reset email body (reset URL with the reset key) for any user. The attacker triggers a password reset for an administrator via the lost-password form, brute-forces recent event IDs through the reaction endpoint to read the resulting user_requested_password_reset_link event, extracts the reset key from context.message, and completes the password reset to take over the administrator account. Exploitation requires an administrator to have first enabled the experimental features option (simple_history_experimental_features_enabled), which is not the default.

    Published
    May 29, 2026
    Affected Product
    Simple History – Track, Log, and Audit WordPress Changes
    Plugin · simple-history
    Affected window
    Versions up to 5.26.0
    Expand for exact coverage and remediation detail.
    Patch status
    Patched release available
    Fixed in 5.27.0
    Recommended next step
    Update to 5.27.0
    Move to a safe release and validate after update.
    Detailed remediation and version lists stay hidden until expanded.
    Affected if you're using
    Versions up to 5.26.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.27.0
    Update to this version or a newer safe release.
    What to do

    Update to version 5.27.0, or a newer patched version

    Affected versions
    Versions up to 5.26.0
    Safe / patched versions
    5.27.0
  • Plugin High Patched: Yes CVSS 8.8/10
    Spectra Gutenberg Blocks <= 2.19.25 - Authenticated (Contributor+) Remote Code Execution via Arbitrary PHP Function Call via Block Attributes

    The Spectra Gutenberg Blocks – Website Builder for the Block Editor plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 2.19.25. This makes it possible for authenticated attackers, with Contributor-level access and above, to execute code on the server. Exploitation requires a two-block payload embedded in post content: the first block registers a fake uagb/-prefixed block type with an attacker-specified render_callback, and the second block of the same fake type triggers invocation of that callback via call_user_func() during sequential block rendering in the same page request.

    Published
    May 29, 2026
    Affected Product
    Spectra Gutenberg Blocks – Website Builder for the Block Editor
    Plugin · ultimate-addons-for-gutenberg
    Affected window
    Versions up to 2.19.25
    Expand for exact coverage and remediation detail.
    Patch status
    Patched release available
    Fixed in 2.19.26
    Recommended next step
    Update to 2.19.26
    Move to a safe release and validate after update.
    Detailed remediation and version lists stay hidden until expanded.
    Affected if you're using
    Versions up to 2.19.25
    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
    2.19.26
    Update to this version or a newer safe release.
    What to do

    Update to version 2.19.26, or a newer patched version

    Affected versions
    Versions up to 2.19.25
    Safe / patched versions
    2.19.26
  • Plugin Medium Patched: Yes CVSS 5.3/10
    Rank Math SEO – AI SEO Tools to Dominate SEO Rankings <= 1.0.271 - Missing Authorization to Unauthenticated Homepage Settings Modification

    The Rank Math SEO – AI SEO Tools to Dominate SEO Rankings plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on the update_site_editor_homepage function in all versions up to, and including, 1.0.271. This makes it possible for unauthenticated attackers to modify several plugin settings including homepage title, meta description, breadcrumbs label, and social media metadata, which can have severe impact on SEO rankings and display malicious content across all site pages where breadcrumbs are used.

    Published
    May 28, 2026
    Affected Product
    Rank Math SEO – AI SEO Tools to Dominate SEO Rankings
    Plugin · seo-by-rank-math
    Affected window
    Versions up to 1.0.271
    Expand for exact coverage and remediation detail.
    Patch status
    Patched release available
    Fixed in 1.0.271.1
    Recommended next step
    Update to 1.0.271.1
    Move to a safe release and validate after update.
    Detailed remediation and version lists stay hidden until expanded.
    Affected if you're using
    Versions up to 1.0.271
    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.0.271.1
    Update to this version or a newer safe release.
    What to do

    Update to version 1.0.271.1, or a newer patched version

    Affected versions
    Versions up to 1.0.271
    Safe / patched versions
    1.0.271.1
  • Plugin Medium Patched: Yes CVSS 5.3/10
    Contact Form 7 – PayPal & Stripe Add-on <= 2.4.9 - Unauthenticated Payment Bypass via Insufficient Verification of Data Authenticity via PayPal IPN Handler ('invoice'/'mc_gross' Verification)

    The Contact Form 7 – PayPal & Stripe Add-on plugin for WordPress is vulnerable to Payment Bypass via Insufficient Verification of Data Authenticity in all versions up to, and including, 2.4.9. Although `cf7pp_paypal_ipn_handler()` correctly validates IPN authenticity by posting back to PayPal with `cmd=_notify-validate`, it fails to compare the IPN payload's `mc_gross` (payment amount), `mc_currency`, or `receiver_email` fields against the corresponding stored order values before passing the attacker-controlled `invoice` field directly to `cf7pp_complete_payment()`, which marks the order completed after only an integer cast with no amount verification. This makes it possible for unauthenticated attackers to mark arbitrary high-value pending orders as fully paid by making a minimal real PayPal payment and crafting an IPN whose `invoice` parameter references the targeted order, effectively completing purchases without tendering the required payment amount.

    Published
    May 28, 2026
    Affected Product
    Contact Form 7 – PayPal & Stripe Add-on
    Plugin · contact-form-7-paypal-add-on
    Affected window
    Versions up to 2.4.9
    Expand for exact coverage and remediation detail.
    Patch status
    Patched release available
    Fixed in 2.4.10
    Recommended next step
    Update to 2.4.10
    Move to a safe release and validate after update.
    Detailed remediation and version lists stay hidden until expanded.
    Affected if you're using
    Versions up to 2.4.9
    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
    2.4.10
    Update to this version or a newer safe release.
    What to do

    Update to version 2.4.10, or a newer patched version

    Affected versions
    Versions up to 2.4.9
    Safe / patched versions
    2.4.10
  • Plugin Medium Patched: Yes CVSS 4.9/10
    Frontend Admin by DynamiApps <= 3.28.28 - Authenticated (Administrator+) SQL Injection via 'order' Parameter

    The Frontend Admin by DynamiApps plugin for WordPress is vulnerable to generic SQL Injection via the 'order' parameter in all versions up to, and including, 3.28.28 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with administrator-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. Exploitation requires that the attacker also supply a valid 'orderby' parameter in the same request, as this is necessary to reach the vulnerable code path that processes and concatenates the 'order' value into the SQL query.

    Published
    May 28, 2026
    Affected Product
    Frontend Admin by DynamiApps
    Plugin · acf-frontend-form-element
    Affected window
    Versions up to 3.28.8
    Expand for exact coverage and remediation detail.
    Patch status
    Patched release available
    Fixed in 3.28.29
    Recommended next step
    Update to 3.28.29
    Move to a safe release and validate after update.
    Detailed remediation and version lists stay hidden until expanded.
    Affected if you're using
    Versions up to 3.28.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
    3.28.29
    Update to this version or a newer safe release.
    What to do

    Update to version 3.28.29, or a newer patched version

    Affected versions
    Versions up to 3.28.8
    Safe / patched versions
    3.28.29
  • Plugin High Patched: Yes CVSS 8.1/10
    Media Library Assistant <= 3.35 - Cross-Site Request Forgery via Bulk Action Form

    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.

    Published
    May 28, 2026
    Affected Product
    Media Library Assistant
    Plugin · media-library-assistant
    Affected window
    Versions up to 3.35
    Expand for exact coverage and remediation detail.
    Patch status
    Patched release available
    Fixed in 3.36
    Recommended next step
    Update to 3.36
    Move to a safe release and validate after update.
    Detailed remediation and version lists stay hidden until expanded.
    Affected if you're using
    Versions up to 3.35
    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
    3.36
    Update to this version or a newer safe release.
    What to do

    Update to version 3.36, or a newer patched version

    Affected versions
    Versions up to 3.35
    Safe / patched versions
    3.36
  • Plugin Medium Patched: Yes CVSS 6.4/10
    The Plus Addons for Elementor <= 6.4.15 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'carousel_direction' Parameter

    The Plus Addons for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'carousel_direction' parameter of the Carousel Anything widget in versions up to, and including, 6.4.15 This is due to insufficient output escaping in the render() function, where the carousel_direction value is placed into an unquoted HTML attribute (dir=) allowing attribute injection despite the use of esc_attr(). 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
    May 28, 2026
    Affected Product
    The Plus Addons for Elementor – Addons for Elementor, Page Templates, Widgets, Mega Menu, WooCommerce
    Plugin · the-plus-addons-for-elementor-page-builder
    Affected window
    Versions up to 6.4.15
    Expand for exact coverage and remediation detail.
    Patch status
    Patched release available
    Fixed in 6.4.16
    Recommended next step
    Update to 6.4.16
    Move to a safe release and validate after update.
    Detailed remediation and version lists stay hidden until expanded.
    Affected if you're using
    Versions up to 6.4.15
    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.4.16
    Update to this version or a newer safe release.
    What to do

    Update to version 6.4.16, or a newer patched version

    Affected versions
    Versions up to 6.4.15
    Safe / patched versions
    6.4.16
  • Plugin High Patched: Yes CVSS 7.2/10
    Link Whisper Free <= 0.9.0 - Unauthenticated Stored Cross-Site Scripting

    The Link Whisper Free plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the user_id parameter in all versions up to, and including, 0.9.0 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
    May 28, 2026
    Affected Product
    Link Whisper Free
    Plugin · link-whisper
    Affected window
    Versions up to 0.9.0
    Expand for exact coverage and remediation detail.
    Patch status
    Patched release available
    Fixed in 0.9.1
    Recommended next step
    Update to 0.9.1
    Move to a safe release and validate after update.
    Detailed remediation and version lists stay hidden until expanded.
    Affected if you're using
    Versions up to 0.9.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
    0.9.1
    Update to this version or a newer safe release.
    What to do

    Update to version 0.9.1, or a newer patched version

    Affected versions
    Versions up to 0.9.0
    Safe / patched versions
    0.9.1
  • Plugin Critical Patched: Yes CVSS 9.8/10
    OTP Login With Phone Number, OTP Verification <= 1.8.60 - Unauthenticated Authentication Bypass via Firebase OTP Verification

    The OTP Login With Phone Number, OTP Verification plugin for WordPress is vulnerable to authentication bypass in versions 1.8.50 through 1.8.60. This is due to the Firebase verification flow in the `lwp_ajax_register` AJAX handler not binding the Firebase session to the phone number supplied in the request. The `idehweb_lwp_activate_through_firebase()` function validates that a Firebase OTP session is legitimate, but the `phoneNumber` returned by Firebase is never compared against the victim's stored phone number. This makes it possible for unauthenticated attackers to authenticate as any user who has a phone number stored in user meta, including administrators, by verifying their own Firebase session and supplying the victim's phone number in the same request.

    Published
    May 28, 2026
    Affected Product
    OTP Login With Phone Number, OTP Verification
    Plugin · login-with-phone-number
    Affected window
    1.8.50 through 1.8.60
    Expand for exact coverage and remediation detail.
    Patch status
    Patched release available
    Fixed in 1.8.61
    Recommended next step
    Update to 1.8.61
    Move to a safe release and validate after update.
    Detailed remediation and version lists stay hidden until expanded.
    Affected if you're using
    1.8.50 through 1.8.60
    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.8.61
    Update to this version or a newer safe release.
    What to do

    Update to version 1.8.61, or a newer patched version

    Affected versions
    1.8.50 through 1.8.60
    Safe / patched versions
    1.8.61
Coverage Hubs

Browse high-interest plugin and theme vulnerability hubs.

Use hub pages to review all indexed records for a single WordPress plugin or theme instead of scanning the global feed one advisory at a time.

36,430 indexed records 14,624 tracked plugins 1,637 tracked themes
Security Guides

Start with the WordPress security topics already showing search demand.

Browse practical guides for WordPress security audit, WooCommerce security, hardening, brute force protection, monitoring, and incident response.

Browse Blog