CVE-2026-96886

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

GHSA-xm8x-c5rq-f7r4 ↗EUVD-2026-89626 ↗

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.
Course Booking System >= 7.0, < 7.0.9
fixed in 7.0.9
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
ETK-2026-510, permanent identifier
17d 04h 07msince last run
1h 31mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+90h39m
0
+2h
+4h
+6h
+8h
+10h

description

Course Booking System WordPress plugin versions before 7.0.9 expose the booking export without authentication. An unauthenticated attacker can download customer names, email addresses, and billing addresses for course bookings. The issue affects sites with the plugin installed at a version earlier than 7.0.9.

mitigation

Upgrade Course Booking System to version 7.0.9 or later. Restrict public access to the affected WordPress site until the update is applied.

fixed in 7.0.9

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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.21%10th percentile
agent run time
1h 31m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-30 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-09-30 06:00Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-510",
  "cve_id": "CVE-2026-96886",
  "display_id": "CVE-2026-96886",
  "ghsa_id": "GHSA-xm8x-c5rq-f7r4",
  "euvd_id": "EUVD-2026-89626",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated booking export data exposure in Course Booking System",
  "summary": "Course Booking System WordPress plugin versions before 7.0.9 expose the booking export without authentication. An unauthenticated attacker can download customer names, email addresses, and billing addresses for course bookings. The issue affects sites with the plugin installed at a version earlier than 7.0.9.",
  "mitigation": "Upgrade Course Booking System to version 7.0.9 or later. Restrict public access to the affected WordPress site until the update is applied.",
  "vendor": null,
  "product": "Course Booking System",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 7.0, < 7.0.9"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "7.0.9"
      ],
      "package_name": "Course Booking System",
      "purl": null
    }
  ],
  "cwes": [
    200
  ],
  "cvss_score": 5.3,
  "cvss_src": "nvd",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
  "epss_score": 0.0021,
  "epss_percentile": 0.1005,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 91.2602785,
  "t0_at": "2026-09-30T06:00:26.004000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-09-30T06:00:26.004000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-30T06:00:26.004000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-96886"
    }
  }
}

published 2026-10-03 23:08Z
last change 2026-10-21 04:45Z

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.