CVE-2026-93399

validatedZero produced an exploit or a check.

GHSA-rmc5-xv4j-mvf8 ↗EUVD-2026-86544 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+1h13mkevAttacks confirmed in the real world.0d
ladela Online Scheduling and Appointment Booking System – Bookly <= 28.2
CWE-639 Authorization Bypass Through User-Controlled Key
ETK-2026-200, permanent identifier
+5.9dTTV
38mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal −0.3dcve.org publicationkev+0dpublic poc+0.1dcheck available+5.9dagent stopped
+2d
+4d

description

Bookly for WordPress through version 28.2 is affected by an insecure direct object reference in several booking AJAX actions. An unauthenticated attacker may access booking and calendar information associated with other orders and delete non-completed bookings. Exploitation requires the affected AJAX endpoints to be reachable and relies on predictable order identifiers.

mitigation

Update Bookly to a vendor release newer than 28.2 once a verified fix is available. Until then, restrict public access to the affected booking AJAX functionality or disable the plugin if that can be done safely.

check
available
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.
deterministic
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.37%29th percentile
agent run time
38m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-25 06:39Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
+1h13m
Δ to kevAttacks confirmed in the real world.
0d

outcome

Check only, differential: the check fires on the vulnerable build and is silent on the patched one.

source signals

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

  1. 2026-09-25
    vulncheck_kev: trigger signal, started the run
  2. 2026-09-25 00:00Z
  3. 2026-09-25 06:39Z
  4. 2026-10-01 07:22Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-200",
  "cve_id": "CVE-2026-93399",
  "display_id": "CVE-2026-93399",
  "ghsa_id": "GHSA-rmc5-xv4j-mvf8",
  "euvd_id": "EUVD-2026-86544",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated insecure direct object reference in Bookly",
  "summary": "Bookly for WordPress through version 28.2 is affected by an insecure direct object reference in several booking AJAX actions. An unauthenticated attacker may access booking and calendar information associated with other orders and delete non-completed bookings. Exploitation requires the affected AJAX endpoints to be reachable and relies on predictable order identifiers.",
  "mitigation": "Update Bookly to a vendor release newer than 28.2 once a verified fix is available. Until then, restrict public access to the affected booking AJAX functionality or disable the plugin if that can be done safely.",
  "vendor": "ladela",
  "product": "Online Scheduling and Appointment Booking System – Bookly",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 28.2"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Online Scheduling and Appointment Booking System – Bookly",
      "purl": null
    }
  ],
  "cwes": [
    639
  ],
  "cvss_score": 9.1,
  "cvss_src": "nvd",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H",
  "epss_score": 0.0037,
  "epss_percentile": 0.2952,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": false,
  "pipeline_minutes": 37.96338213333333,
  "t0_at": "2026-09-25T06:39:55.951000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-01T04:18:26.400495+00:00",
      "days": 5.901741313599537,
      "is_lower_bound": false,
      "measured_at": "2026-09-25T06:39:55.951000+00:00",
      "url": null
    },
    "kev": {
      "at": "2026-09-25T00:00:00+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-25T06:39:55.951000+00:00",
      "precision": "day",
      "url": "https://vulncheck.com/cve/CVE-2026-93399"
    },
    "public_poc": {
      "at": "2026-09-25T07:53:19+00:00",
      "days": 0.05096121527777778,
      "is_lower_bound": false,
      "measured_at": "2026-09-25T06:39:55.951000+00:00",
      "url": "https://github.com/murrez/CVE-2026-93399"
    },
    "trigger_signal": {
      "at": "2026-09-25T00:00:00+00:00",
      "days": -0.2777309143518519,
      "is_lower_bound": false,
      "measured_at": "2026-09-25T06:39:55.951000+00:00",
      "url": "https://vulncheck.com/cve/CVE-2026-93399"
    }
  }
}

published 2026-10-01 03:40Z
last change 2026-10-21 05:00Z

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.