CVE-2026-78392

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

GHSA-rhhx-6v4c-mf5v ↗EUVD-2026-108018 ↗

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.
Link Library < 7.9.6
fixed in 7.9.6
ETK-2026-2409Zero's internal tracking ID, independent of the CVE number., permanent identifier
24msince last run
23mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+3h43m
0
+2h
+6h
+8h
+10h
+12h

description

Link Library for WordPress versions before 7.9.6 mishandle link-field content in link previews. A user with the Contributor role or higher can cause script content to be stored and run in a visitor's browser when the preview is opened; the preview can be accessed without authentication, including for unapproved submissions.

mitigation

Update the Link Library WordPress plugin to version 7.9.6 or later. Until updated, restrict Contributor-level access and limit access to link preview pages.

fixed in 7.9.6

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
23m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-22 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: no remotely reachable path found.

source signals

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

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-2409",
  "cve_id": "CVE-2026-78392",
  "display_id": "CVE-2026-78392",
  "ghsa_id": "GHSA-rhhx-6v4c-mf5v",
  "euvd_id": "EUVD-2026-108018",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Stored cross-site scripting in Link Library",
  "summary": "Link Library for WordPress versions before 7.9.6 mishandle link-field content in link previews. A user with the Contributor role or higher can cause script content to be stored and run in a visitor's browser when the preview is opened; the preview can be accessed without authentication, including for unapproved submissions.",
  "mitigation": "Update the Link Library WordPress plugin to version 7.9.6 or later. Until updated, restrict Contributor-level access and limit access to link preview pages.",
  "vendor": null,
  "product": "Link Library",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 7.9.6"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "7.9.6"
      ],
      "package_name": "Link Library",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": null,
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 23.045254333333332,
  "t0_at": "2026-10-22T06:00:18.482000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-22T06:00:18.482000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-22T06:00:18.482000+00:00",
      "url": "https://github.com/advisories/GHSA-rhhx-6v4c-mf5v"
    }
  }
}

published 2026-10-22 08:46Z
last change 2026-10-22 09:51Z

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.