CVE-2026-97316

validatedZero produced an exploit or a check.

GHSA-vxvw-9xhx-r2mf ↗EUVD-2026-89627 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Broken Link Notifier >= 1.3.1, < 2.0.0.1
fixed in 2.0.0.1
CWE-918 Server-Side Request Forgery (SSRF)
ETK-2026-509, permanent identifier
+3.7dTTV
24mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0dcheck available+3.7dagent stopped
0
+1d
+2d
+3d
+4d

description

Broken Link Notifier versions before 2.0.0.1 can follow redirects to destinations that bypass its internal-address protections. An unauthenticated attacker may cause the WordPress host to send requests to internal services when the plugin checks an attacker-controlled link.

mitigation

Update Broken Link Notifier to version 2.0.0.1 or later.

fixed in 2.0.0.1

check
available
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
deterministic
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.21%10th percentile
agent run time
24m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-30 06:00Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Check only, differential: the check fires on the vulnerable build and is silent on the patched one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-09-30 06:00Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-97316

{
  "etk_id": "ETK-2026-509",
  "cve_id": "CVE-2026-97316",
  "display_id": "CVE-2026-97316",
  "ghsa_id": "GHSA-vxvw-9xhx-r2mf",
  "euvd_id": "EUVD-2026-89627",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated server-side request forgery in Broken Link Notifier",
  "summary": "Broken Link Notifier versions before 2.0.0.1 can follow redirects to destinations that bypass its internal-address protections. An unauthenticated attacker may cause the WordPress host to send requests to internal services when the plugin checks an attacker-controlled link.",
  "mitigation": "Update Broken Link Notifier to version 2.0.0.1 or later.",
  "vendor": null,
  "product": "Broken Link Notifier",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.3.1, < 2.0.0.1"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2.0.0.1"
      ],
      "package_name": "Broken Link Notifier",
      "purl": null
    }
  ],
  "cwes": [
    918
  ],
  "cvss_score": 5.8,
  "cvss_src": "nvd",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N",
  "epss_score": 0.0021,
  "epss_percentile": 0.1055,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": false,
  "pipeline_minutes": 24.3602776,
  "t0_at": "2026-09-30T06:00:26.188000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-03T23:30:21.486697+00:00",
      "days": 3.7291122534375,
      "is_lower_bound": false,
      "measured_at": "2026-09-30T06:00:26.188000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-09-30T06:00:26.188000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-30T06:00:26.188000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-97316"
    }
  }
}

published 2026-10-03 23:05Z
last change 2026-10-21 13:29Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.