CVE-2026-87973

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

GHSA-627c-fv9j-9cxm ↗EUVD-2026-90513 ↗

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.9.9, < 1.10.2
fixed in 1.10.2
CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
ETK-2026-532, permanent identifier
16d 16h 06msince last run
37mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+96h28m
0
+2h
+4h
+6h
+8h
+10h

description

If-So Dynamic Content versions before 1.10.2 improperly handle conversion names displayed in the analytics page. An editor-level user may cause script to run in the browser session of a higher-privileged user who views that page.

mitigation

Update If-So Dynamic Content to version 1.10.2 or later. Until updated, restrict editor access and avoid viewing analytics entries created by untrusted users.

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.
yes, high privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.12%1st percentile
agent run time
37m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-01 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-01 06:00Z
    ghsa: trigger signal, started the run
  2. 2026-10-01 06:00Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-532",
  "cve_id": "CVE-2026-87973",
  "display_id": "CVE-2026-87973",
  "ghsa_id": "GHSA-627c-fv9j-9cxm",
  "euvd_id": "EUVD-2026-90513",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Stored cross-site scripting in If-So Dynamic Content",
  "summary": "If-So Dynamic Content versions before 1.10.2 improperly handle conversion names displayed in the analytics page. An editor-level user may cause script to run in the browser session of a higher-privileged user who views that page.",
  "mitigation": "Update If-So Dynamic Content to version 1.10.2 or later. Until updated, restrict editor access and avoid viewing analytics entries created by untrusted users.",
  "vendor": null,
  "product": "If-So Dynamic Content",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.9.9, < 1.10.2"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.10.2"
      ],
      "package_name": "If-So Dynamic Content",
      "purl": null
    }
  ],
  "cwes": [
    79
  ],
  "cvss_score": 3.1,
  "cvss_src": "nvd",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:N",
  "epss_score": 0.0012,
  "epss_percentile": 0.019,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 36.812833866666665,
  "t0_at": "2026-10-01T06:00:24.703000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-01T06:00:24.703000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-01T06:00:24.703000+00:00",
      "url": "https://github.com/advisories/GHSA-627c-fv9j-9cxm"
    }
  }
}

published 2026-10-04 05:27Z
last change 2026-10-21 15:37Z

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.