HomeWordPress vulnerabilitiesBroken Link Notifier
Broken Link Notifier vulnerabilities
Broken Link Notifier has 3 known vulnerabilities in this database. The most recent published record is dated 30 Sep 2026.
- Known vulnerabilities
- 3
- Active installs
- 1,000+
- Latest version
- 2.0.0.1
- Last updated
- 24 Sep 2026
- Most recent
- 30 Sep 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Server-side request forgery (SSRF) CVE-2026-97316 | Medium 5.8 | Before 2.0.0.1 | Fixed in 2.0.0.1 | 7 d ago |
| CSV injection CVE-2025-6838 | Medium 4.1 | Up to 1.3.0 | Fixed in a later version (latest 2.0.0.1) | 11 Jul 2025 |
| Server-side request forgery (SSRF) CVE-2025-6851 | High 7.2 | Before 1.3.1 | Fixed in 1.3.1 | 11 Jul 2025 |
Read the published descriptions
- CVE-2026-97316, 30 Sep 2026
- The Broken Link Notifier WordPress plugin before 2.0.0.1 does not re-validate the destination of redirects when checking links, allowing unauthenticated attackers to bypass its internal-address filter and make the server send requests to internal services. CVE record
- CVE-2025-6838, 11 Jul 2025
- 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 into exported CSV files, which can result in code execution when these files are downloaded and opened on a local system with a vulnerable configuration. CVE record
- CVE-2025-6851, 11 Jul 2025
- 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 record
What to do if you run Broken Link Notifier
If you run Broken Link Notifier, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Broken Link Notifier vulnerabilities
Free. We email you when a new vulnerability is published for Broken Link Notifier, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.