HomeWordPress vulnerabilitiesBroken Link Checker
Broken Link Checker vulnerabilities
Broken Link Checker has 13 known vulnerabilities in this database. The most recent published record is dated 2 Sep 2026.
- Known vulnerabilities
- 13
- Active installs
- 500,000+
- Latest version
- 2.4.14.1
- Last updated
- 31 Aug 2026
- Most recent
- 2 Sep 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-75528 | High 7.2 | Up to 2.4.13 | Fixed in a later version (latest 2.4.14.1) | 2 Sep 2026 |
| Remote code execution CVE-2026-18937 | Critical 9.0 | Before 2.4.12 | Fixed in 2.4.12 | 19 Aug 2026 |
| SQL injection CVE-2026-39466 | High 7.6 | Up to 2.4.7 | Fixed in a later version (latest 2.4.14.1) | 8 Apr 2026 |
| Broken access control CVE-2025-4047 | Medium 4.3 | Up to 2.4.4 | Fixed in a later version (latest 2.4.14.1) | 3 Jun 2025 |
| Server-side request forgery (SSRF) CVE-2024-10903 | Medium 4.7 | Before 2.4.2 | Fixed in 2.4.2 | 26 Dec 2024 |
| Cross-site scripting (XSS) CVE-2024-8981 | High 7.1 | Up to 2.4.0 | Fixed in a later version (latest 2.4.14.1) | 1 Oct 2024 |
| Cross-site scripting (XSS) CVE-2014-125105 | Low 2.4 | Up to 1.10.1 | Fixed in a later version (latest 2.4.14.1) | 5 Jun 2023 |
| Cross-site scripting (XSS) CVE-2015-10098 | Low 3.5 | Before 1.10.6 | Fixed in 1.10.6 | 8 Apr 2023 |
| Cross-site scripting (XSS) CVE-2022-3922 | Medium 4.8 | Before 1.11.20 | Fixed in 1.11.20 | 28 Dec 2022 |
| PHP object injection CVE-2022-2438 | High 7.2 | Before 1.11.17 | Fixed in 1.11.17 | 6 Sep 2022 |
| Cross-site scripting (XSS) CVE-2019-17207 | Medium 5.4 | Up to 1.11.8 | Fixed in a later version (latest 2.4.14.1) | 18 Oct 2019 |
| Cross-site scripting (XSS) CVE-2019-16521 | Medium 6.1 | Up to 1.11.8 | Fixed in a later version (latest 2.4.14.1) | 16 Oct 2019 |
| Cross-site scripting (XSS) CVE-2015-5057 | Medium 6.1 | Up to 1.10.8 | Fixed in a later version (latest 2.4.14.1) | 18 Aug 2017 |
Read the published descriptions
- CVE-2026-75528, 2 Sep 2026
- 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. CVE record
- CVE-2026-18937, 19 Aug 2026
- The Broken Link Checker WordPress plugin before 2.4.12 does not limit which query variables it accepts from user input on sites using plain permalinks, allowing unauthenticated users to overwrite arbitrary PHP global variables, and to execute arbitrary code on the server when a classic (non-block) is active. CVE record
- CVE-2026-39466, 8 Apr 2026
- Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in WPMU DEV - Your All-in-One WordPress Platform Broken Link Checker broken-link-checker allows Blind SQL Injection.This issue affects Broken Link Checker: from n/a through <= 2.4.7. CVE record
- CVE-2025-4047, 3 Jun 2025
- The Broken Link Checker plugin for WordPress is vulnerable to unauthorized data access due to a missing capability check on the ajax_full_status and ajax_dashboard_status functions in all versions up to, and including, 2.4.4. This makes it possible for authenticated attackers, with Subscriber-level access and above, to view the plugin's status. CVE record
- CVE-2024-10903, 26 Dec 2024
- The Broken Link Checker WordPress plugin before 2.4.2 does not validate a the link URLs before making a request to them, which could allow admin users to perform SSRF attack, for example on a multisite installation. CVE record
- CVE-2024-8981, 1 Oct 2024
- The Broken Link Checker plugin for WordPress is vulnerable to Reflected Cross-Site Scripting due to the use of add_query_arg in /app/admin-notices/features/class-view.php without appropriate escaping on the URL in all versions up to, and including, 2.4.0. 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. CVE record
- CVE-2014-125105, 5 Jun 2023
- A vulnerability was found in Broken Link Checker Plugin up to 1.10.1 on WordPress. It has been declared as problematic. Affected by this vulnerability is the function options_page of the file core/core.php of the component Settings Page. The manipulation of the argument exclusion_list/blc_custom_fields leads to cross site scripting. The attack can be launched remotely. Upgrading to version 1.10.2 is able to address this issue. The patch is named 90615fe9b0b6f9e6fb254d503c302e53a202e561. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-230659. CVE record
- CVE-2015-10098, 8 Apr 2023
- A vulnerability was found in Broken Link Checker Plugin up to 1.10.5 on WordPress. It has been rated as problematic. Affected by this issue is the function print_module_list/show_warnings_section_notice/status_text/ui_get_action_links. The manipulation leads to cross site scripting. The attack may be launched remotely. Upgrading to version 1.10.6 is able to address this issue. The name of the patch is f30638869e281461b87548e40b517738b4350e47. It is recommended to upgrade the affected component. The identifier of this vulnerability is VDB-225152. CVE record
- CVE-2022-3922, 28 Dec 2022
- The Broken Link Checker WordPress plugin before 1.11.20 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup) CVE record
- CVE-2022-2438, 6 Sep 2022
- The Broken Link Checker plugin for WordPress is vulnerable to deserialization of untrusted input via the '$log_file' value in versions up to, and including 1.11.16. This makes it possible for authenticated attackers with administrative privileges and above to call files using a PHAR wrapper that will deserialize the data and call arbitrary PHP Objects that can be used to perform a variety of malicious actions granted a POP chain is also present. It also requires that the attacker is successful in uploading a file with the serialized payload. CVE record
- CVE-2019-17207, 18 Oct 2019
- A reflected XSS vulnerability was found in includes/admin/table-printer.php in the broken-link-checker (aka Broken Link Checker) plugin 1.11.8 for WordPress. This allows unauthorized users to inject client-side JavaScript into an admin-only WordPress page via the wp-admin/tools.php?page=view-broken-links s_filter parameter in a search action. CVE record
- CVE-2019-16521, 16 Oct 2019
- The broken-link-checker plugin through 1.11.8 for WordPress (aka Broken Link Checker) is susceptible to Reflected XSS due to improper encoding and insertion of an HTTP GET parameter into HTML. The filter function on the page listing all detected broken links can be exploited by providing an XSS payload in the s_filter GET parameter in a filter_id=search request. NOTE: this is an end-of-life product. CVE record
- CVE-2015-5057, 18 Aug 2017
- Cross-site scripting (XSS) vulnerability exists in the Wordpress admin panel when the Broken Link Checker plugin before 1.10.9 is installed. CVE record
What to do if you run Broken Link Checker
If you run Broken Link Checker, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Broken Link Checker vulnerabilities
Free. We email you when a new vulnerability is published for Broken Link Checker, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.