Quick answers
- Is CVE-2026-97316 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-97316 being exploited in the wild.
- How severe is CVE-2026-97316?
- Informational severity, published 30 September 2026.
- Which products and versions are affected?
- WPScan Broken Link Notifier 1.3.1 through 2.0.0.
- Is there a fix for CVE-2026-97316?
- A patch was published on 2026-09-28: Fixed in version 2.0.0.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-97316 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-97316?
- Check whether you run WPScan Broken Link Notifier at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The plugin fails to re-validate the final destination of HTTP redirects when checking links, allowing unauthenticated attackers to bypass the internal-address filter via a redirect chain. An attacker can craft a public URL that redirects to an internal IP or service, causing the vulnerable server to send requests to internal endpoints. This is a server-side request forgery (SSRF) vulnerability that requires no authentication and can be exploited over the network.
Affected products
- WPScan Broken Link Notifier 1.3.1 through 2.0.0
Timeline
- 2026-09-28: disclosed
- 2026-09-28: patched: Fixed in version 2.0.0.1