CVE-2025-6851: The Broken Link Notifier plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up

Q: How do I fix CVE-2025-6851?

broken link notifier: upgrade to 1.3.1. Exact commands for each OS are on this page.

Q: Is CVE-2025-6851 being exploited?

CVE-2025-6851 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-6851 affect?

CVE-2025-6851 affects broken link notifier. Severity is high (CVSS 7.2). 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

Q: How urgent is CVE-2025-6851?

Priority 44/100. High severity; Remotely exploitable, no login, no user action

This month

HIGH 7.2REMOTEUPGRADE

CVE-2025-6851 is a high-severity flaw (CVSS 7.2) affecting broken link notifier. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.2 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.7% (top 46%)
CISA exploited list	No
Weakness	CWE-918
Published	2025-07-11
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: pluginrx

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-07-11 09:15 UTCPublished CVE record published
2026-06-17 10:02 UTCUpdated Record last modified

pluginrx broken link notifier UPGRADE

Affected: < 1.3.1

Fixed in: 1.3.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy broken-link-notifier || rpm -q broken-link-notifier || broken-link-notifier --version

2. UPGRADE to 1.3.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade broken-link-notifier

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade broken-link-notifier

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Nuclei scan template: WordPress Broken Link Notifier < 1.3.1 - Unauthenticated SSRF

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-6851?

broken link notifier: upgrade to 1.3.1. Exact commands for each OS are on this page.

Is CVE-2025-6851 being exploited?

CVE-2025-6851 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-6851 affect?

CVE-2025-6851 affects broken link notifier. Severity is high (CVSS 7.2). 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

How urgent is CVE-2025-6851?

Priority 44/100. High severity; Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs