CVE-2026-82214

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

GHSA-8883-4cxp-cmxm ↗EUVD-2026-114589 ↗

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.
Quick Event Manager >= 8.4.6, < 9.19
fixed in 9.19
ETK-2026-3154Zero's internal tracking ID, independent of the CVE number., permanent identifier
6h 55msince last run
19mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h48m
0
+4h
+6h
+8h
+10h
+12h

description

Quick Event Manager for WordPress releases before 9.19 expose non-public post content through calendar exports. An unauthenticated remote party may retrieve information from draft or private posts when the affected export functionality is reachable.

mitigation

Upgrade Quick Event Manager to version 9.19 or later. Until upgraded, restrict access to or disable calendar export functionality where feasible.

fixed in 9.19

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.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
19m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-31 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, 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-10-31 06:00Z
    ghsa: trigger signal, started the run
  2. 2026-10-31 06:00Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-3154",
  "cve_id": "CVE-2026-82214",
  "display_id": "CVE-2026-82214",
  "ghsa_id": "GHSA-8883-4cxp-cmxm",
  "euvd_id": "EUVD-2026-114589",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated post disclosure in Quick Event Manager",
  "summary": "Quick Event Manager for WordPress releases before 9.19 expose non-public post content through calendar exports. An unauthenticated remote party may retrieve information from draft or private posts when the affected export functionality is reachable.",
  "mitigation": "Upgrade Quick Event Manager to version 9.19 or later. Until upgraded, restrict access to or disable calendar export functionality where feasible.",
  "vendor": null,
  "product": "Quick Event Manager",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 8.4.6, < 9.19"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "9.19"
      ],
      "package_name": "Quick Event Manager",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 18.9034564,
  "t0_at": "2026-10-31T06:00:23.431000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-31T06:00:23.431000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-31T06:00:23.431000+00:00",
      "url": "https://github.com/advisories/GHSA-8883-4cxp-cmxm"
    }
  }
}

published 2026-10-31 07:29Z
last change 2026-10-31 13:36Z

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.