CVE-2026-115673

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

GHSA-xvj9-569f-63gr ↗EUVD-2026-117911 ↗

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.
Anti-Spam, Spam FireWall by CleanTalk < 6.91
fixed in 6.91
ETK-2026-3697Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 42msince last run
36mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+0h56m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Anti-Spam, Spam FireWall by CleanTalk versions before 6.91 improperly handle commenter-controlled data on the administrative spam-review page. An unauthenticated attacker may cause script to run in an administrator's browser if that administrator reviews a flagged comment.

mitigation

Upgrade Anti-Spam, Spam FireWall by CleanTalk to version 6.91 or later. Limit access to the administrative spam-review interface until the update is complete.

fixed in 6.91

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.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
36m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-06 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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-3697",
  "cve_id": "CVE-2026-115673",
  "display_id": "CVE-2026-115673",
  "ghsa_id": "GHSA-xvj9-569f-63gr",
  "euvd_id": "EUVD-2026-117911",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Stored cross-site scripting in Anti-Spam, Spam FireWall by CleanTalk",
  "summary": "Anti-Spam, Spam FireWall by CleanTalk versions before 6.91 improperly handle commenter-controlled data on the administrative spam-review page. An unauthenticated attacker may cause script to run in an administrator's browser if that administrator reviews a flagged comment.",
  "mitigation": "Upgrade Anti-Spam, Spam FireWall by CleanTalk to version 6.91 or later. Limit access to the administrative spam-review interface until the update is complete.",
  "vendor": null,
  "product": "Anti-Spam, Spam FireWall by CleanTalk",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 6.91"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "6.91"
      ],
      "package_name": "Anti-Spam, Spam FireWall by CleanTalk",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 35.81248861666667,
  "t0_at": "2026-11-06T06:00:27.640000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-06T06:00:27.640000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-06T06:00:27.640000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-115673"
    }
  }
}

published 2026-11-06 06:20Z
last change 2026-11-06 08:12Z

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.