EUVD-2026-69940
GHSA-f27h-6jwq-4c83
Severity by source
AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N
High privilege required to access the editor component; scope change reflects SSRF reaching internal network services beyond the WordPress trust boundary; no availability impact.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
Lifecycle Timeline
1DescriptionCVE.org
Editor Server Side Request Forgery (SSRF) in Broken Link Checker <= 2.4.14 versions.
AnalysisAI
Server-Side Request Forgery in the Broken Link Checker WordPress plugin (WPMU Dev, versions ≤ 2.4.14) allows high-privileged authenticated users to coerce the server into issuing arbitrary HTTP requests from its editor component. The CVSS scope-change flag (S:C) indicates the forged requests can reach resources outside the WordPress application boundary, such as cloud instance metadata endpoints or internal network services. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires an authenticated WordPress user with high privileges - specifically Administrator-level access (CVSS PR:H) - to interact with the Broken Link Checker editor component and submit a malicious URL. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS base score of 5.5 is moderated heavily by PR:H, meaning only highly privileged WordPress principals (typically Administrators) can trigger the flaw - substantially narrowing the attack surface compared to unauthenticated SSRF. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | Update Broken Link Checker to the version released after 2.4.14 per the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/broken-link-checker/vulnerability/wordpress-broken-link-checker-plugin-2-4-14-server-side-request-forgery-ssrf-vulnerability); the exact patched version number is not independently confirmed from the available input data. … Detailed patch versions, workarounds, and compensating controls in full report. |
Threat intelligence, references, and detailed analysis are available after sign-in.
More in Broken Link Checker
View allThe broken-link-checker plugin through 1.11.8 for WordPress (aka Broken Link Checker) is susceptible to Reflected XSS du
Unauth. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low
A reflected XSS vulnerability was found in includes/admin/table-printer.php in the broken-link-checker (aka Broken Link
The Broken Link Checker WordPress plugin before 1.11.20 does not sanitise and escape some of its settings, which could a
The Broken Link Checker WordPress plugin before 2.4.2 does not validate a the link URLs before making a request to them,
Blind SQL injection in WPMU DEV Broken Link Checker WordPress plugin versions ≤2.4.7 allows authenticated high-privilege
The Broken Link Checker plugin for WordPress is vulnerable to deserialization of untrusted input via the '$log_file' val
Stored XSS in the Broken Link Checker WordPress plugin (versions ≤ 2.4.13) allows unauthenticated attackers to inject pe
Cross-site scripting (XSS) vulnerability exists in the Wordpress admin panel when the Broken Link Checker plugin before
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WPMU DEV Broken Li
Same weakness CWE-918 – Server-Side Request Forgery (SSRF)
View allShare
External POC / Exploit Code
Leaving vuln.today