CVE-2026-87971

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

GHSA-qp9g-v8qg-cx5q ↗EUVD-2026-94188 ↗

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.
If-So Dynamic Content >= 1.4.4, < 1.10.2
fixed in 1.10.2
CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
ETK-2026-1310Zero's internal tracking ID, independent of the CVE number., permanent identifier
8d 22h 35msince last run
52mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+120h13m
0
+2h
+4h
+6h
+8h
+10h

description

If-So Dynamic Content versions before 1.10.2 for WordPress are affected by reflected cross-site scripting on an administrative page. An attacker may cause JavaScript to run in a logged-in user's browser if that user opens a crafted link.

mitigation

Update If-So Dynamic Content to version 1.10.2 or later. Until updated, limit administrative users from opening untrusted links.

fixed in 1.10.2

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.15%3rd percentile
agent run time
52m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-07 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

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-07 06:00Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1310",
  "cve_id": "CVE-2026-87971",
  "display_id": "CVE-2026-87971",
  "ghsa_id": "GHSA-qp9g-v8qg-cx5q",
  "euvd_id": "EUVD-2026-94188",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Reflected cross-site scripting in If-So Dynamic Content",
  "summary": "If-So Dynamic Content versions before 1.10.2 for WordPress are affected by reflected cross-site scripting on an administrative page. An attacker may cause JavaScript to run in a logged-in user's browser if that user opens a crafted link.",
  "mitigation": "Update If-So Dynamic Content to version 1.10.2 or later. Until updated, limit administrative users from opening untrusted links.",
  "vendor": null,
  "product": "If-So Dynamic Content",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.4.4, < 1.10.2"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.10.2"
      ],
      "package_name": "If-So Dynamic Content",
      "purl": null
    }
  ],
  "cwes": [
    79
  ],
  "cvss_score": 7.1,
  "cvss_src": "nvd",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L",
  "epss_score": 0.0015,
  "epss_percentile": 0.0347,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 52.28490251666667,
  "t0_at": "2026-10-07T06:00:08.472000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-07T06:00:08.472000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-07T06:00:08.472000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-87971"
    }
  }
}

published 2026-10-12 05:20Z
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.