WordPress plugin · Updated daily · Source: Wordfence Intelligence

Broken Link Checker vulnerabilities: affected versions and fixes

Broken Link Checker has 500,000+ active installs. Here are its publicly disclosed vulnerabilities, whether your version is affected, and what to do now.

Broken Link Checker at a glance

  • 16 publicly disclosed vulnerabilities, 4 of them rated High or Critical. The most recent was disclosed on Oct 15, 2026.
  • Ranked #127 by popularity on WordPress.org (500,000+ active installs).
  • The latest version is 2.4.15.1 (released Nov 17, 2026). The most recent security fix shipped in 2.4.15.
  • Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
  • The first thing to do: update to the latest version and turn on automatic updates.

Check your Broken Link Checker version

Enter the Broken Link Checker version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.

Your version number is compared on this page only. It is not sent anywhere.

Get an email when a new vulnerability is disclosed

We'll tell you when a new vulnerability is disclosed in “Broken Link Checker”, with the version that fixes it. Free, email address only, stop any time.

We use your email address only for these alerts. Privacy policy

Want every plugin and theme on your site checked daily?

With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.

View the plugin on wordpress.orgGet a free in-depth scan

How to check whether your site is affected

  1. 1

    Find your version

    In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Broken Link Checker”.

  2. 2

    Compare it with the list below

    If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.

  3. 3

    Update

    Click “Update now” to move to the latest version (2.4.15.1). Taking a backup first is a good idea.

  4. 4

    Turn on automatic updates

    On the same screen, click “Enable auto-updates” so future fixes are installed automatically.

Known Broken Link Checker vulnerabilities

  • Broken Link Checker <= 2.4.14.1 - Unauthenticated Arbitrary Shortcode Execution via parser_callback

    Other weakness · CVE-2026-96562

    Affected versions: ≤ 2.4.14.1

    Fixed in: 2.4.15

    Severity: Medium 6.5 · Disclosed Oct 15, 2026

  • Broken Link Checker <= 2.4.14.1 - Unauthenticated Arbitrary HTML Attribute Injection

    Other weakness · CVE-2026-102389

    Affected versions: ≤ 2.4.14.1

    Fixed in: 2.4.15

    Severity: Medium 5.3 · Disclosed Oct 13, 2026

  • Broken Link Checker <= 2.4.14 - Authenticated (Editor+) Server-Side Request Forgery

    Server-side request forgery (SSRF) · CVE-2026-84772

    Affected versions: ≤ 2.4.14

    Fixed in: 2.4.14.1

    Severity: Medium 5.5 · Disclosed Sep 2, 2026

  • Broken Link Checker <= 2.4.13 - Unauthenticated Stored Cross-Site Scripting via Comment Author URL / Link Log

    Cross-site scripting (XSS) · CVE-2026-75528

    Affected versions: ≤ 2.4.13

    Fixed in: 2.4.13.1

    Severity: High 7.2 · Disclosed Sep 1, 2026

  • Broken Link Checker < 2.4.12 - Unauthenticated Remote Code Execution

    Remote code execution · CVE-2026-18937

    Affected versions: < 2.4.12

    Fixed in: 2.4.12

    Severity: Critical 9.8 · Disclosed Aug 21, 2026

  • Broken Link Checker <= 2.4.7 - Authenticated (Editor+) SQL Injection

    SQL injection · CVE-2026-39466

    Affected versions: ≤ 2.4.7

    Fixed in: 2.4.8

    Severity: Medium 4.9 · Disclosed Mar 26, 2026

  • Broken Link Checker <= 2.4.4 - Missing Autorization to Authenticated (Subscriber+) Plugin Status Dashboard View

    Missing authorization · CVE-2025-4047

    Affected versions: ≤ 2.4.4

    Fixed in: 2.4.5

    Severity: Medium 4.3 · Disclosed Jun 2, 2025

  • Broken Link Checker <= 2.4.1 - Authenticated (Admin+) Server-Side Request Forgery

    Server-side request forgery (SSRF) · CVE-2024-10903

    Affected versions: ≤ 2.4.1

    Fixed in: 2.4.2

    Severity: Medium 5.5 · Disclosed Dec 5, 2024

  • Broken Link Checker <= 2.4.0 - Reflected Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2024-8981

    Affected versions: ≤ 2.4.0

    Fixed in: 2.4.1

    Severity: High 7.1 · Disclosed Sep 30, 2024

  • Broken Link Checker <= 2.2.3 - Authenticated (Administrator+) Stored Cross-Site Scripting via settings

    Cross-site scripting (XSS) · CVE-2024-25592

    Affected versions: ≤ 2.2.3

    Fixed in: 2.2.4

    Severity: Medium 4.4 · Disclosed Feb 12, 2024

  • Broken Link Checker <= 1.11.19 - Authenticated (Administrator+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2022-3922

    Affected versions: ≤ 1.11.19

    Fixed in: 1.11.20

    Severity: Medium 5.5 · Disclosed Nov 11, 2022

  • Broken Link Checker <= 1.11.16 - Authenticated (Admin+) PHAR Deserialization

    PHP object injection · CVE-2022-2438

    Affected versions: ≤ 1.11.16

    Fixed in: 1.11.17

    Severity: High 7.2 · Disclosed Jul 18, 2022

  • Broken Link Checker <= 1.11.8 - Reflected Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2019-17207

    Affected versions: < 1.11.9

    Fixed in: 1.11.9

    Severity: Medium 6.1 · Disclosed Oct 14, 2019

  • Broken Link Checker <= 1.10.8 - Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2015-5057

    Affected versions: < 1.10.9

    Fixed in: 1.10.9

    Severity: Medium 6.1 · Disclosed Jun 29, 2015

  • Broken Link Checker < 1.10.6 - Reflected Cross Site Scripting

    Cross-site scripting (XSS) · CVE-2015-10098

    Affected versions: < 1.10.6

    Fixed in: 1.10.6

    Severity: Medium 5.3 · Disclosed Apr 20, 2015

  • Broken Link Checker < 1.10.2 - Authenticated (Admin+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2014-125105

    Affected versions: < 1.10.2

    Fixed in: 1.10.2

    Severity: Medium 5.5 · Disclosed Dec 5, 2014

Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Oct 15, 2026.

Most common weaknesses in Broken Link Checker

Cross-site scripting (XSS)

8 issues

An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.

Server-side request forgery (SSRF)

2 issues

Your server can be made to send requests to other systems on the attacker’s behalf, including internal ones.

Remote code execution

1 issue

An attacker can run code of their choice on your server. This is the most dangerous kind: it usually means a full takeover of the site.

Frequently asked questions

Is Broken Link Checker safe to use?

Broken Link Checker is a well-known plugin with 500,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (2.4.15.1) and turn on automatic updates.

How do I find which version of Broken Link Checker my site is running?

In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.

Could updating break my site?

Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.

Can I check all my other plugins too?

Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.

Check every plugin and theme automatically, every day

Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.

Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.

← All plugin vulnerabilitiesBroken Link Checker on WordPress.org