Broken Link Checker <= 1.11.16 - Authenticated (Admin+) PHAR Deserialization
Strategic Overview
- Status
- Patched in 1.11.17
- Affected Plugin
- Broken Link Checker
- Affected Version
<= 1.11.16- CVSS
- 7.2High
- Weakness type
- CWE-502 · Deserialization of Untrusted Data
- CVE
CVE-2022-2438
At a glance
CVE-2022-2438 is a high-severity Deserialization of Untrusted Data vulnerability in the Broken Link Checker WordPress plugin, affecting versions <= 1.11.16. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Admin level or above. The issue is fixed in version 1.11.17; sites on affected versions should update now. Disclosed July 2022, reported by Rasoul Jahanshahi.
Vulnerability Overview
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.
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 interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-502: Deserialization of Untrusted Data
Reaching this weakness in Broken Link Checker <= 1.11.16 takes an account at Admin level or above. Deserialization of untrusted data means the application reconstructs objects from input a caller controls, letting the attacker choose which classes get instantiated and what their properties hold.
A workable chain turns deserialization into file writes, deletions or code execution, depending on what the loaded classes do in their magic methods. For Broken Link Checker the fix is 1.11.17: builds <= 1.11.16 are affected, anything from 1.11.17 onward is not.
Remediation
Update to version 1.11.17, or a newer patched version
How does WordSec protect against this?
An attacker needs Admin access first, so the firewall sees the attempt as traffic from a logged-in account: 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 1.11.17 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Related records
Other vulnerabilities in Broken Link Checker
- 9.8CVE-2026-18937: Broken Link Checker < 2.4.12 Remote Code Execution
CVE-2026-18937 - 7.2CVE-2026-75528: Broken Link Checker <= 2.4.13 Stored XSS
CVE-2026-75528 - 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