WordPress security changelog
HIGH CVE-2025-6851 Analyzed

Broken Link Notifier: Server-side request forgery

Broken Link Notifier is affected by server-side request forgery. The vulnerable path is reachable without authentication. The vulnerable server can be induced to make attacker-selected network requests.

CVE / CNA score 7.2 CVSS 3.1 · security@wordfence.com
NVD score 6.5 CVSS 3.1 · nvd@nist.gov
Component
Broken Link Notifier
Plugin slug
broken-link-notifier
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Jul 11, 2025
Weakness
CWE-918 — Server-Side Request Forgery (SSRF)

This CVE was published Jul 11, 2025 and is one of 3 known issues for this plugin.

Update, patch or deactivate.

Update Broken Link Notifier to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Technical description

The Broken Link Notifier plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 1.3.0 via the ajax_blinks() function which ultimately calls the check_url_status_code() function. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

NVD vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Primary and upstream sources