ETK-2026-4720Zero's internal tracking ID, independent of the CVE number.

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

GHSA-62qw-cq6m-mrh6 ↗

no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−1.4dkevAttacks confirmed in the real world.
other go:github.com/siyuan-note/siyuan v3.8.11-beta.1 (the release that carries the fix for GHSA-x62v-7955-xx6v); the same unfiltered push path is present in v3.8.10; which predates the fix
fixed in v3.8.11
CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
ETK-2026-4720Zero's internal tracking ID, independent of the CVE number., no cve assigned
22h 58msince last run
12mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org, not yet published
trigger signal −32h35mpublic poc−32h35mwaiting for further signals−22h58m
−12h
0

description

SiYuan versions before v3.8.11 can retain attacker-supplied event-handler attributes in imported workspace content and later apply them during a block attribute update. An attacker who can cause a malicious import and have a user or collaborator update the affected block may execute script in that user's session; desktop builds may expose the user's local privileges.

mitigation

Upgrade SiYuan to v3.8.11. Until all clients are updated, do not import untrusted .sy.zip content and limit workspace editing to trusted collaborators.

fixed in v3.8.11

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.
–
agent run time
12m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
−1.4d
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-11-17 13:20Z
  2. 2026-11-17 13:20Z

this entry in the feed

GET /api/v1/feed/ETK-2026-4720

{
  "etk_id": "ETK-2026-4720",
  "cve_id": null,
  "display_id": "ETK-2026-4720",
  "ghsa_id": "GHSA-62qw-cq6m-mrh6",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Stored event-handler injection in SiYuan blocks",
  "summary": "SiYuan versions before v3.8.11 can retain attacker-supplied event-handler attributes in imported workspace content and later apply them during a block attribute update. An attacker who can cause a malicious import and have a user or collaborator update the affected block may execute script in that user's session; desktop builds may expose the user's local privileges.",
  "mitigation": "Upgrade SiYuan to v3.8.11. Until all clients are updated, do not import untrusted .sy.zip content and limit workspace editing to trusted collaborators.",
  "vendor": "other",
  "product": "go:github.com/siyuan-note/siyuan",
  "affected": [
    {
      "affected_notes": [
        "v3.8.11-beta.1 (the release that carries the fix for GHSA-x62v-7955-xx6v)",
        "the same unfiltered push path is present in v3.8.10",
        "which predates the fix"
      ],
      "affected_ranges": [],
      "ecosystem": "other",
      "fixed_versions": [
        "v3.8.11"
      ],
      "package_name": "siyuan-note/siyuan",
      "purl": null
    }
  ],
  "cwes": [
    79
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 12.122000733333333,
  "t0_at": null,
  "signals": {
    "public_poc": {
      "at": "2026-11-17T13:20:17+00:00",
      "days": -1.3579562088541668,
      "is_lower_bound": true,
      "measured_at": "2026-11-18T21:55:44.466123+00:00",
      "url": "https://github.com/siyuan-note/siyuan/security/advisories/GHSA-62qw-cq6m-mrh6"
    },
    "trigger_signal": {
      "at": "2026-11-17T13:20:17+00:00",
      "days": -1.3579562088541668,
      "is_lower_bound": true,
      "measured_at": "2026-11-18T21:55:44.466123+00:00",
      "url": "https://github.com/siyuan-note/siyuan/security/advisories/GHSA-62qw-cq6m-mrh6"
    }
  }
}

published 2026-11-17 22:59Z
last change 2026-11-18 21:43Z

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.