What is the CVSS score of CVE-2025-6851?

CVE-2025-6851 has a CVSS 3.1 base score of 7.2 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N. EPSS exploitation probability: 1.8%.

Which versions of PHP are affected by CVE-2025-6851?

The Broken Link Notifier WordPress plugin contains a Server-Side Request Forgery vulnerability that allows unauthenticated attackers to make unauthorized web requests from your organization's…. A patch is available.

Is there a public PoC exploit available for CVE-2025-6851?

Yes, a public proof-of-concept exploit is available for CVE-2025-6851. Prioritise patching immediately. EPSS: 1.8%.

How to fix or mitigate CVE-2025-6851?

Within 24 hours: Identify all WordPress installations using Broken Link Notifier plugin version 1.3.0 or earlier and disable the plugin immediately. Within 7 days: Update the plugin to version 1.3.1 or later once available, or remove the plugin if unused; test functionality in a staging environment before production deployment. Within 30 days: Conduct a security audit of affected systems to identify any unauthorized requests made through the vulnerability and review web server logs for suspicious activity during the vulnerability window.

PHP CVE-2025-6851

EUVD-2025-21125 HIGH

Server-Side Request Forgery (SSRF) (CWE-918)

2025-07-11 security@wordfence.com

PHP WordPress SSRF Broken Link Notifier Wordpress Plugin

7.2

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.2 HIGH

AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

EUVD ID Assigned

Mar 16, 2026 - 08:17 euvd

EUVD-2025-21125

Analysis Generated

Mar 16, 2026 - 08:17 vuln.today

Patch released

Mar 16, 2026 - 08:17 nvd

Patch available

CVE Published

Jul 11, 2025 - 09:15 nvd

HIGH 7.2

DescriptionCVE.org

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.

AnalysisAI

A SSRF vulnerability in for WordPress is vulnerable to Server-Side Request Forgery in all (CVSS 7.2). High severity vulnerability requiring prompt remediation. Vendor patch is available.