CVE-2025-6851

Broken Link Notifier <= 1.3.0 - Unauthenticated Server-Side Request Forgery

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.

Category

7.2
CVSS
Severity: High
CVSS 3.1 •
EPSS 0.04%
Affected: apos37 Broken Link Notifier
Published at:
Updated at:

References

Frequently Asked Questions

What is the severity of CVE-2025-6851?
CVE-2025-6851 has been scored as a high severity vulnerability.
How to fix CVE-2025-6851?
To fix CVE-2025-6851, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2025-6851 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2025-6851 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2025-6851?
CVE-2025-6851 affects apos37 Broken Link Notifier.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.