Scan WordPress with VulnTitan.
Free plugin for live checks. Pro adds scheduled scans, malware detection, integrity monitoring, alerts and guided remediation.
-
Appointment Booking Calendar <= 1.6.10.0 - Unauthenticated SQL Injection via 'fields' Parameter
The Appointment Booking Calendar — Simply Schedule Appointments Booking Plugin plugin for WordPress is vulnerable to SQL Injection via the 'fields' parameter in all versions up to, and including, 1.6.10.0 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. 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, including usernames, email addresses, and password hashes.
PublishedMar 18, 2026Affected ProductAppointment Booking Calendar — Simply Schedule Appointments Booking PluginPlugin · simply-schedule-appointmentsAffected if you're usingVersions up to 1.6.10.0Check the full report if you need exact branch-by-branch coverage.Patch availableYesA fixed release is listed for this issue.Fixed in1.6.10.2Update to this version or a newer safe release.What to doUpdate to version 1.6.10.2, or a newer patched version
Affected versionsVersions up to 1.6.10.0Safe / patched versions1.6.10.2 -
Instant Popup Builder <= 1.1.7 - Unauthenticated Arbitrary Shortcode Execution via 'token' Parameter
The Instant Popup Builder plugin for WordPress is vulnerable to Unauthenticated Arbitrary Shortcode Execution in all versions up to and including 1.1.7. This is due to the handle_email_verification_page() function constructing a shortcode string from user-supplied GET parameters (token, email) and passing it to do_shortcode() without properly sanitizing square bracket characters, combined with missing authorization checks on the init hook. While sanitize_text_field() and esc_attr() are applied, neither function strips or escapes square bracket characters ([ and ]). WordPress's shortcode regex uses [^\]\/]* to match content inside shortcode tags, meaning a ] character in the token value prematurely closes the shortcode tag. This makes it possible for unauthenticated attackers to inject and execute arbitrary registered shortcodes by crafting a malicious token parameter containing ] followed by arbitrary shortcode syntax.
PublishedMar 18, 2026Affected ProductInstant Popup Builder – Powerful Popup Maker for Opt-ins, Email Newsletters & Lead GenerationPlugin · instant-popup-builderAffected if you're usingVersions up to 1.1.7Check the full report if you need exact branch-by-branch coverage.Patch availableYesA fixed release is listed for this issue.Fixed in1.1.8Update to this version or a newer safe release.What to doUpdate to version 1.1.8, or a newer patched version
Affected versionsVersions up to 1.1.7Safe / patched versions1.1.8 -
Add Custom Fields to Media <= 2.0.3 - Cross-Site Request Forgery to Custom Field Deletion via 'delete' Parameter
The Add Custom Fields to Media plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.0.3. This is due to missing nonce validation on the field deletion functionality in the admin display template. The plugin properly validates a nonce for the 'add field' operation (line 24-36), but the 'delete field' operation (lines 38-49) processes the $_GET['delete'] parameter and calls update_option() without any nonce verification. This makes it possible for unauthenticated attackers to delete arbitrary custom media fields via a forged request, granted they can trick a site administrator into performing an action such as clicking on a link.
PublishedMar 18, 2026Affected ProductAdd Custom Fields to MediaPlugin · add-custom-fields-to-mediaAffected if you're usingVersions up to 2.0.3Check the full report if you need exact branch-by-branch coverage.Patch availableYesA fixed release is listed for this issue.Fixed in2.0.4Update to this version or a newer safe release.What to doUpdate to version 2.0.4, or a newer patched version
Affected versionsVersions up to 2.0.3Safe / patched versions2.0.4 -
Draft List <= 2.6.2 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'display_name' Parameter
The Simple Draft List plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'display_name' post meta (Custom Field) in all versions up to and including 2.6.2. This is due to insufficient input sanitization and output escaping on the author display name when no author URL is present. The plugin accesses `$draft_data->display_name` which, because `display_name` is not a native WP_Post property, triggers WP_Post::__get() and resolves to `get_post_meta($post_id, 'display_name', true)`. When the `user_url` meta field is empty, the `$author` value is assigned to `$author_link` on line 383 without any escaping (unlike line 378 which uses `esc_html()` for the `{{author}}` tag, and line 381 which uses `esc_html()` when a URL is present). This unescaped value is then inserted into the shortcode output via `str_replace()`. 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 a page containing the `[drafts]` shortcode with the `{{author+link}}` template tag.
PublishedMar 18, 2026Affected ProductDraft ListPlugin · simple-draft-listAffected if you're usingVersions up to 2.6.2Check the full report if you need exact branch-by-branch coverage.Patch availableYesA fixed release is listed for this issue.Fixed in2.6.3Update to this version or a newer safe release.What to doUpdate to version 2.6.3, or a newer patched version
Affected versionsVersions up to 2.6.2Safe / patched versions2.6.3 -
SlimStat Analytics <= 5.3.5 - Unauthenticated Stored Cross-Site Scripting via 'fh'
The SlimStat Analytics plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'fh' (fingerprint) parameter in all versions up to, and including, 5.3.5 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.
PublishedMar 18, 2026Affected ProductSlimStat AnalyticsPlugin · wp-slimstatAffected if you're usingVersions up to 5.3.5Check the full report if you need exact branch-by-branch coverage.Patch availableYesA fixed release is listed for this issue.Fixed in5.4.0Update to this version or a newer safe release.What to doUpdate to version 5.4.0, or a newer patched version
Affected versionsVersions up to 5.3.5Safe / patched versions5.4.0 -
Download Manager <= 3.3.49 - Missing Authorization to Authenticated (Subscriber+) User Email Enumeration via 'user' Parameter
The Download Manager plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the 'reviewUserStatus' function in all versions up to, and including, 3.3.49. This makes it possible for authenticated attackers, with Subscriber-level access and above, to retrieve sensitive information for any user on the site including email addresses, display names, and registration dates.
PublishedMar 18, 2026Affected ProductDownload ManagerPlugin · download-managerAffected if you're usingVersions up to 3.3.49Check the full report if you need exact branch-by-branch coverage.Patch availableYesA fixed release is listed for this issue.Fixed in3.3.50Update to this version or a newer safe release.What to doUpdate to version 3.3.50, or a newer patched version
Affected versionsVersions up to 3.3.49Safe / patched versions3.3.50 -
Info Cards <= 2.0.7 - Authenticated (Contributor+) Stored Cross-Site Scripting via Block Attributes
The Info Cards – Add Text and Media in Card Layouts plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'btnUrl' parameter within the Info Cards block in all versions up to, and including, 2.0.7. This is due to insufficient input validation on URL schemes, specifically the lack of javascript: protocol filtering. The block's render.php passes all attributes as JSON to the frontend via a data-attributes HTML attribute using esc_attr(wp_json_encode()), which prevents HTML attribute injection but does not validate URL protocols within the JSON data. The client-side view.js then renders the btnUrl value directly as an href attribute on anchor elements without any protocol sanitization. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject javascript: URLs that execute arbitrary web scripts when a user clicks the rendered button link.
PublishedMar 18, 2026Affected ProductInfo Cards – Add Text and Media in Card LayoutsPlugin · info-cardsAffected if you're usingVersions up to 2.0.7Check the full report if you need exact branch-by-branch coverage.Patch availableYesA fixed release is listed for this issue.Fixed in2.0.8Update to this version or a newer safe release.What to doUpdate to version 2.0.8, or a newer patched version
Affected versionsVersions up to 2.0.7Safe / patched versions2.0.8 -
Yoast Duplicate Post <= 4.5 - Authenticated (Contributor+) Missing Authorization to Arbitrary Post Duplication and Overwrite
The Yoast Duplicate Post plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the clone_bulk_action_handler() and republish_request() functions in all versions up to, and including, 4.5. This makes it possible for authenticated attackers, with Contributor-level access and above, to duplicate any post on the site including private, draft, and trashed posts they shouldn't have access to. Additionally, attackers with Author-level access and above can use the Rewrite & Republish feature to overwrite any published post with their own content.
PublishedMar 17, 2026Affected ProductYoast Duplicate PostPlugin · duplicate-postAffected if you're usingVersions up to 4.5Check the full report if you need exact branch-by-branch coverage.Patch availableYesA fixed release is listed for this issue.Fixed in4.6Update to this version or a newer safe release.What to doUpdate to version 4.6, or a newer patched version
Affected versionsVersions up to 4.5Safe / patched versions4.6 -
Writeprint Stylometry <= 0.1 - Reflected Cross-Site Scripting via 'p' Parameter
The Writeprint Stylometry plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'p' GET parameter in all versions up to and including 0.1. This is due to insufficient input sanitization and output escaping in the bjl_wprintstylo_comments_nav() function. The function directly outputs the $_GET['p'] parameter into an HTML href attribute without any escaping. This makes it possible for authenticated attackers with Contributor-level permissions or higher to inject arbitrary web scripts in pages that execute if they can successfully trick another user into performing an action such as clicking on a link.
PublishedMar 17, 2026Affected ProductWriteprint StylometryPlugin · writeprint-stylometryAffected if you're usingVersions up to 0.1Check the full report if you need exact branch-by-branch coverage.Patch availableNoNo fixed release is listed in the feed yet.Fixed inNot publishedWatch for a vendor release before treating the issue as fixed.What to doNo known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
Affected versionsVersions up to 0.1Safe / patched versionsNo safe version is published yet. -
[CR]Paid Link Manager <= 0.5 - Reflected Cross-Site Scripting
The [CR]Paid Link Manager plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the URL path in all versions up to, and including, 0.5 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.
PublishedMar 17, 2026Affected Product[CR]Paid Link ManagerPlugin · crpaid-link-managerAffected if you're usingVersions up to 0.5Check the full report if you need exact branch-by-branch coverage.Patch availableYesA fixed release is listed for this issue.Fixed in0.6Update to this version or a newer safe release.What to doUpdate to version 0.6, or a newer patched version
Affected versionsVersions up to 0.5Safe / patched versions0.6
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.