CVE-2026-102389: Broken Link Checker remote code execution vulnerability
medium 6.5 published 2026-10-15
- Affected versions
- 2.4.14.1 and older
- Fixed in
- 2.4.15
- Latest version
- 2.4.15
- Severity
- Medium · CVSS 6.5
- Active installs
- 500,000+
- Type
- Remote code execution
What an attacker needs
- Access: None. No account or login is needed (per the CVSS score).
- Interaction: It also needs someone on the site (often an admin) to click a link, open a page or submit a form the attacker prepared.
CVSS vector (score by Patchstack): CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
What to do now
- Update Broken Link Checker to 2.4.15 or newer: Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- Not sure which version you run? Check your version against every known Broken Link Checker issue.
With WP-CLI:
wp plugin get broken-link-checker --field=version. - If you ran an affected version and something looks off (new admin users, spam pages, redirects), run the free scan below.
The advisory
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.
References
- NVD CVE-2026-102389 nvd.nist.gov
- Patchstack advisory patchstack.com
Related
Ran an affected version? Check your site for signs of a hack
The free scan reads the public side of your site and looks for spam pages, hidden redirects, injected scripts and blacklist entries. No login, no install, about a minute.
Where this data comes from
- CVE record, score and references: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Versions and install counts: wordpress.org/plugins/broken-link-checker (Plugins API), fetched 2026-11-01.
- The summary, “what an attacker needs” and “what to do” sections are our plain-English reading of the record and the plugin's release history; the quoted description is the record's own text. Spot an error? Email Daniel.