Quick answers
- Is CVE-2026-84772 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-84772 being exploited in the wild.
- How severe is CVE-2026-84772?
- Medium severity, with a CVSS score of 5.5, published 2 September 2026.
- Which products and versions are affected?
- WPMU DEV Broken Link Checker <= 2.4.14.
- Is there a fix for CVE-2026-84772?
- A patch was published on 2026-09-02: Fix available in version 2.4.14.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-84772 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-84772?
- Check whether you run WPMU DEV Broken Link Checker at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a Server Side Request Forgery (SSRF) in the Broken Link Checker WordPress plugin versions 2.4.14 and earlier. An attacker with editor privileges can craft requests that cause the plugin to make unintended server-side HTTP connections to internal systems, services, or cloud metadata endpoints. The attack vector requires authentication (editor role) and network access to the WordPress site. An attacker can bypass network segmentation and leak sensitive data from internal systems or cloud infrastructure. The vulnerability was patched in version 2.4.14.1; users should update immediately.
Affected products
- WPMU DEV Broken Link Checker <= 2.4.14
Timeline
- 2026-08-25: disclosed: Reported to Patchstack by Ananda Dhakal
- 2026-09-02: advisory: Published by Patchstack
- 2026-09-02: patched: Fix available in version 2.4.14.1