Editor-level SSRF via undisclosed request validation flaw
Published Sep 2, 2026 · Updated Sep 3, 2026
Server-side request forgery in WPMU DEV Broken Link Checker 2.4.14 and earlier allows remote authenticated users to send arbitrary requests. The CNA and vendor changelog do not identify the affected handler or explain how an Editor-controlled URL bypasses request validation. Editor-level WordPress access is required; the server can be induced to contact arbitrary domains and expose data from reachable services.
Summary
What happened
Server-side request forgery in WPMU DEV Broken Link Checker 2.4.14 and earlier allows remote authenticated users to send arbitrary requests. The CNA and vendor changelog do not identify the affected handler or explain how an Editor-controlled URL bypasses request validation. Editor-level WordPress access is required; the server can be induced to contact arbitrary domains and expose data from reachable services.
The record
- CVE
- CVE-2026-84772
- Published
- Sep 2, 2026
- Updated
- Sep 3, 2026
- Vendor
- WPMU DEV
- Product
- Broken Link Checker
- Classifications
- CWE-918, CAPEC-664
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 2, 2026CVE publishedPublication date reported by the CVE source.
- Sep 3, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=n/a <=2.4.14 changes=[{"at":"2.4.14.1","status":"unaffected"}]
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo