CVE Intelligence

Wpmudev Broken Link Checker vulnerabilities

🔔 Create alert RSS Version checker

Published CVEs affecting Wpmudev Broken Link Checker: 4 record(s), with affected versions and fixes.

CVE-2026-96562 Medium · 6.5 CWE-94 Oct 16, 2026
Broken Link Checker <= 2.4.14.1 - Unauthenticated Arbitrary Shortcode Execution via parser_callback
The The Broken Link Checker plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 2.4.14.1. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes. Exploitation requires that a submitted comment containing the shortcode payload in an href or src attribute is approved through the site's normal comment moderation workflow; once approved, the shortcode is executed automatically via WP-Cron without any further attacker interaction.
CVE-2026-102389 Medium · 6.5 CWE-94 Oct 15, 2026
WordPress Broken Link Checker plugin <= 2.4.14.1 - Content Injection vulnerability
Improper Control of Generation of Code ('Code Injection') vulnerability in WPMU DEV Broken Link Checker broken-link-checker allows Code Injection.This issue affects Broken Link Checker: from n/a through 2.4.14.1.
CVE-2026-84772 Medium · 5.5 CWE-918 Sep 2, 2026
WordPress Broken Link Checker plugin <= 2.4.14 - Server Side Request Forgery (SSRF) vulnerability
Editor Server Side Request Forgery (SSRF) in Broken Link Checker <= 2.4.14 versions.
CVE-2026-75528 High · 7.2 CWE-79 Sep 2, 2026
Broken Link Checker <= 2.4.13 - Unauthenticated Stored Cross-Site Scripting via Comment Author URL / Link Log
The Broken Link Checker plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Author URL / Link Log in all versions up to, and including, 2.4.13 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. Exploitation requires an administrator to perform the plugin's standard dismiss-and-recheck workflow on a link submitted by the attacker via the WordPress comment author URL field, after which the attacker's HTTP server issues a redirect to a URL containing an HTML/JavaScript payload that is stored verbatim in the link log.