VulnTitan VulnTitan Security command center
Plugin Vulnerability Hub
Plugin 3 known issues Latest disclosed Jan 29, 2026

Broken Link Notifier Vulnerabilities

Review known vulnerability records for the WordPress plugin Broken Link Notifier (`broken-link-notifier`), including severity, CVE references, affected versions, and patch status.

Recent tracked CVEs on this page include CVE-2026-25408, CVE-2025-6851 and CVE-2025-6838, so operators can jump from disclosure to patch validation without scanning the full feed first.

View on WordPress.org Back to Feed
Known Records
3
High or Critical
1
Patch Coverage
100%
Last Updated
Mar 06, 2026
Related Security Guides

Use these guides while reviewing Broken Link Notifier fixes

Pair this plugin vulnerability hub with practical WordPress hardening, scanner, and patch workflow guidance.

Hardening
WordPress hardening checklist for exposed plugins

Review patch cadence, privileged access, XML-RPC exposure, backups, and monitoring controls.
Plugin Security
WordPress plugin security basics for patch decisions

Use ownership, update testing, least privilege, and removal criteria to reduce plugin risk.
Scanning
WordPress vulnerability scanner buyer's guide

Compare scanner coverage for plugin CVEs, version detection, alert noise, and remediation workflow.
Patch Decision Workflow

How to prioritize Broken Link Notifier remediation

Use the hub as a decision layer before opening individual records: confirm whether the issue has a CVE, whether a fixed version exists, and whether the affected range overlaps production installs.

Search-Ready Records
3
1. Match the Package
Confirm the installed WordPress plugin slug is broken-link-notifier before acting on any CVE from this cluster.
2. Sort by Severity
Start with 1 high or critical record, then review medium and unrated findings with public references.
3. Check Patch Evidence
3 records include a patch path; verify compatibility before closing the finding.
4. Monitor Gaps
0 records still lack a listed fixed release, so keep this hub in the review queue.
High-Signal Remediation Targets
CVE-2025-6851 High
Server-Side Request Forgery remediation for Broken Link Notifier

Affected range: Versions up to 1.3.0. Fixed version: 1.3.1.

CVE-2026-25408 Medium
Vulnerability remediation for Broken Link Notifier

Affected range: Versions up to 1.3.5. Fixed version: 1.3.6.

CVE-2025-6838 Medium
Vulnerability remediation for Broken Link Notifier

Affected range: Versions up to 1.3.0. Fixed version: 1.3.1.

Priority CVE Quick Links

Fast paths into Broken Link Notifier CVE reports

Start with the highest-signal CVE records for this WordPress plugin before scanning the full vulnerability feed.

Indexed CVEs
3
Tracked CVE Issue Type Affected Versions Fixed Version CVSS
CVE-2025-6851
Broken Link Notifier <= 1.3.0 - Unauthenticated Server-Side Request Forgery
 Server-Side Request Forgery Versions up to 1.3.0 1.3.1 CVSS 7.2
CVE-2026-25408
Broken Link Notifier <= 1.3.5 - Missing Authorization
 Vulnerability Versions up to 1.3.5 1.3.6 CVSS 5.3
CVE-2025-6838
Broken Link Notifier <= 1.3.0 - Authenticated (Contributor+) CSV Injection
 Vulnerability Versions up to 1.3.0 1.3.1 CVSS 4.1
CVE-2025-6851 High 1.3.1
CVE-2025-6851 Broken Link Notifier Server-Side Request Forgery

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

CVE-2026-25408 Medium 1.3.6
CVE-2026-25408 Broken Link Notifier Vulnerability

Broken Link Notifier <= 1.3.5 - Missing Authorization

CVE-2025-6838 Medium 1.3.1
CVE-2025-6838 Broken Link Notifier Vulnerability

Broken Link Notifier <= 1.3.0 - Authenticated (Contributor+) CSV Injection

Coverage Snapshot

What this page helps you verify fast

This hub clusters tracked records for Broken Link Notifier so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.

Patch Visibility
3 records include a published patch path, leaving 0 with no listed safe release yet.
Severity Mix
0 critical and 1 high severity finding.
Recent CVEs
CVE-2026-25408, CVE-2025-6851 and CVE-2025-6838
Reference Workflow
Jump from the hub into the full report when you need remediation notes, exploit context, CVSS vectors, or source references.
Triage First

Open the records most likely to drive action

These recent records surface the CVE strings, patch cues, and direct report links most operators need first.

Known Vulnerabilities

Reports for Broken Link Notifier

Sorted by latest disclosure date so newly published issues surface first.

Plugin Medium Patched: Yes CVE-2026-25408
CVE-2026-25408: Broken Link Notifier <= 1.3.5 - Missing Authorization

The Broken Link Notifier plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on a function in versions up to, and including, 1.3.5. This makes it possible for unauthenticated attackers to perform an unauthorized action.

Published
Jan 29, 2026
Patched Release
1.3.6
Affected Versions
Versions up to 1.3.5
Next Step
Update to 1.3.6 or newer if supported.
Review CVE-2026-25408 fixed version details Open CVE Reference
Plugin High Patched: Yes CVE-2025-6851
CVE-2025-6851: Broken Link Notifier <= 1.3.0 - Unauthenticated Server-Side Request Forgery

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...

Published
Jul 10, 2025
Patched Release
1.3.1
Affected Versions
Versions up to 1.3.0
Next Step
Update to 1.3.1 or newer if supported.
Review CVE-2025-6851 fixed version details Open CVE Reference
Plugin Medium Patched: Yes CVE-2025-6838
CVE-2025-6838: Broken Link Notifier <= 1.3.0 - Authenticated (Contributor+) CSV Injection

The Broken Link Notifier plugin for WordPress is vulnerable to CSV Injection in all versions up to, and including, 1.3.0 via broken links that are later exported. This makes it possible for authenticated attackers, with Contributor-level access and above, to embed untrusted input...

Published
Jul 10, 2025
Patched Release
1.3.1
Affected Versions
Versions up to 1.3.0
Next Step
Update to 1.3.1 or newer if supported.
Review CVE-2025-6838 fixed version details Open CVE Reference