Broken Link Checker <= 2.4.14.1 - Unauthenticated Arbitrary Shortcode Execution via parser_callback
Strategic Overview
- Status
- Patched in 2.4.15
- Affected Plugin
- Broken Link Checker
- Affected Version
<= 2.4.14.1- CVSS
- 6.5Medium
- Weakness type
- CWE-94 · Improper Control of Generation of Code ('Code Injection')
- CVE
CVE-2026-96562
At a glance
CVE-2026-96562 is a medium-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the Broken Link Checker WordPress plugin, affecting versions <= 2.4.14.1. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.4.15; sites on affected versions should update now. Disclosed October 2026, reported by Jakub Herman.
Vulnerability Overview
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.
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-94: Improper Control of Generation of Code ('Code Injection')
Reaching this weakness in Broken Link Checker <= 2.4.14.1 takes no account at all. Code injection means input from a request reaches a language construct that evaluates code, so the attacker's text is executed rather than treated as data.
The injected code runs with the web server's privileges, giving the attacker the same access to the database and filesystem as WordPress itself. For Broken Link Checker the fix is 2.4.15: builds <= 2.4.14.1 are affected, anything from 2.4.15 onward is not.
Remediation
Update to version 2.4.15, 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. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Broken Link Checker 2.4.15 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Login Security
External References
Related records
Same weakness class
Other vulnerabilities in Broken Link Checker
- 7.2CVE-2026-75528: Broken Link Checker <= 2.4.13 Stored XSS
CVE-2026-75528 - 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 - 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-2026-84772: Broken Link Checker <= 2.4.14 SSRF
CVE-2026-84772 - 5.5CVE-2024-10903: Broken Link Checker <= 2.4.1 SSRF
CVE-2024-10903 - 5.5CVE-2022-3922: Broken Link Checker <= 1.11.19 Stored XSS
CVE-2022-3922
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C