CVE-2026-84772

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

2026-09-02 00:00
Ananda Dhakal

Strategic Overview

Status
Patched in 2.4.14.1
Affected Plugin
Broken Link Checker
Affected Version
<= 2.4.14
CVSS
5.5Medium
Weakness type
CWE-918 · Server-Side Request Forgery (SSRF)
CVE
CVE-2026-84772
View all Broken Link Checker vulnerabilities

At a glance

CVE-2026-84772 is a medium-severity Server-Side Request Forgery (SSRF) vulnerability in the Broken Link Checker WordPress plugin, affecting versions <= 2.4.14. It carries a CVSS score of 5.5 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Editor level or above. The issue is fixed in version 2.4.14.1; sites on affected versions should update now. Disclosed September 2026, reported by Ananda Dhakal.

Vulnerability Overview

The Broken Link Checker plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 2.4.14. This makes it possible for authenticated attackers, with editor-level access and above, to make web requests to arbitrary locations originating from the web application which can be used to query and modify information from internal services.

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.

CWE-918: Server-Side Request Forgery (SSRF)

Reaching this weakness in Broken Link Checker <= 2.4.14 takes an account at Editor level or above. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.

The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. For Broken Link Checker the fix is 2.4.14.1: builds <= 2.4.14 are affected, anything from 2.4.14.1 onward is not.

Remediation

Update to version 2.4.14.1, or a newer patched version

How does WordSec protect against this?

An attacker needs Editor 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. None of that substitutes for the fix: Broken Link Checker 2.4.14.1 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-84772https://www.wordfence.com/threat-intel/vulnerabilities/id/6bfdf424-5afd-4af0-a19c-bfb115450747https://nvd.nist.gov/vuln/detail/CVE-2026-84772

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C