Broken Link Checker <= 2.4.13 - Unauthenticated Stored Cross-Site Scripting via Comment Author URL / Link Log
Strategic Overview
- Status
- Patched in 2.4.13.1
- Affected Plugin
- Broken Link Checker
- Affected Version
<= 2.4.13- CVSS
- 7.2High
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2026-75528
At a glance
CVE-2026-75528 is a high-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Broken Link Checker WordPress plugin, affecting versions <= 2.4.13. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.4.13.1; sites on affected versions should update now. Disclosed September 2026, reported by Adrien Brunner.
Vulnerability Overview
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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in Broken Link Checker <= 2.4.13 takes no account at all. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Broken Link Checker the fix is 2.4.13.1: builds <= 2.4.13 are affected, anything from 2.4.13.1 onward is not.
Remediation
Update to version 2.4.13.1, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Broken Link Checker 2.4.13.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Same weakness class
- 6.1CVE-2019-16521: Broken Link Checker <= 1.11.8 Reflected XSS
CVE-2019-16521 - 6.1CVE-2015-5057: Broken Link Checker <= 1.10.8 Cross-Site Scripting
CVE-2015-5057 - 5.5CVE-2022-3922: Broken Link Checker <= 1.11.19 Stored XSS
CVE-2022-3922 - 5.5CVE-2014-125105: Broken Link Checker < 1.10.2 Stored XSS
CVE-2014-125105
Other vulnerabilities in Broken Link Checker
- 9.8CVE-2026-18937: Broken Link Checker < 2.4.12 Remote Code Execution
CVE-2026-18937 - 7.2CVE-2022-2438: Broken Link Checker <= 1.11.16 PHAR Deserialization
CVE-2022-2438 - 7.1CVE-2024-8981: Broken Link Checker <= 2.4.0 Reflected XSS
CVE-2024-8981 - 5.5CVE-2024-10903: Broken Link Checker <= 2.4.1 SSRF
CVE-2024-10903 - 5.4CVE-2019-17207: Broken Link Checker <= 1.11.8 Reflected XSS
CVE-2019-17207 - 5.3CVE-2015-10098: Broken Link Checker < 1.10.6 Reflected XSS
CVE-2015-10098 - 4.9CVE-2026-39466: Broken Link Checker <= 2.4.7 SQL Injection
CVE-2026-39466 - 4.4CVE-2024-25592: Broken Link Checker <= 2.2.3 Stored XSS
CVE-2024-25592
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C