CVE-2026-96671

waiting for further signalsZero needs more public information before it can validate it.

GHSA-926h-pfq9-mqvv ↗EUVD-2026-95611 ↗

no check availablenot proven exploitable
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.
fifu.app Featured Image from URL <= 6.0.7
ETK-2026-1096Zero's internal tracking ID, independent of the CVE number., permanent identifier
11d 08h 43msince last run
37mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+11h02m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Featured Image from URL versions through 6.0.7 are reported to be affected by a cross-site request forgery flaw. An attacker may be able to induce a logged-in user's browser to submit an unintended request; the advisory does not specify the action involved or the permissions required.

mitigation

Update Featured Image from URL to a vendor-confirmed release newer than 6.0.7. Until then, limit administrator access and warn privileged users not to follow untrusted links while signed in.

check
no
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.
contextual
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.13%2nd percentile
agent run time
37m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-09 10: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

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

  1. 2026-10-09 10:00Z
    ghsa: trigger signal, started the run
  2. 2026-10-09 10:00Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-1096",
  "cve_id": "CVE-2026-96671",
  "display_id": "CVE-2026-96671",
  "ghsa_id": "GHSA-926h-pfq9-mqvv",
  "euvd_id": "EUVD-2026-95611",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Cross-site request forgery in Featured Image from URL",
  "summary": "Featured Image from URL versions through 6.0.7 are reported to be affected by a cross-site request forgery flaw. An attacker may be able to induce a logged-in user's browser to submit an unintended request; the advisory does not specify the action involved or the permissions required.",
  "mitigation": "Update Featured Image from URL to a vendor-confirmed release newer than 6.0.7. Until then, limit administrator access and warn privileged users not to follow untrusted links while signed in.",
  "vendor": "fifu.app",
  "product": "Featured Image from URL",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 6.0.7"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "featured-image-from-url",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
  "epss_score": 0.0013,
  "epss_percentile": 0.0239,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 36.81208076666667,
  "t0_at": "2026-10-09T10:00:21.368000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-09T10:00:21.368000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-09T10:00:21.368000+00:00",
      "url": "https://github.com/advisories/GHSA-926h-pfq9-mqvv"
    }
  }
}

published 2026-10-09 20:25Z
last change 2026-10-21 04:45Z

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.