← back to feed
CVE-2026-92245

CVE-2026-92245

validatedZero produced an exploit or a check.

GHSA-3frh-27r2-gj5w ↗EUVD-2026-90464 ↗

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).kevAttacks confirmed in the real world.
croixhaug Simply Schedule Appointments <= 1.6.12.32
CWE-862 Missing Authorization
ETK-2026-203, permanent identifier
cvss7.5cna vendorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
+1h18mTTV
20mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0mcheck available+78magent stopped
0
+15min
+30min
+45min
+60min

description

Simply Schedule Appointments for WordPress through version 1.6.12.32 may expose appointment records to unauthenticated requests. An attacker who can reach the affected REST interface may obtain customer personal data and appointment tokens, and those tokens may allow appointment deletion without logging in.

mitigation

Disable the plugin or restrict unauthenticated access to its appointment REST endpoints until the vendor provides an update. Where removal is not immediately possible, use a reverse proxy or WAF rule to block unauthenticated requests to the affected appointment API path.

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.43%35th percentile
agent run time
20m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-01 03:28Z
Δ 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

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-10-01 03:28Z
    cve_org: trigger signal, started the run
    https://www.cve.org/CVERecord?id=CVE-2026-92245

this entry in the feed

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

{
  "etk_id": "ETK-2026-203",
  "cve_id": "CVE-2026-92245",
  "display_id": "CVE-2026-92245",
  "ghsa_id": "GHSA-3frh-27r2-gj5w",
  "euvd_id": "EUVD-2026-90464",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated information disclosure in Simply Schedule Appointments",
  "summary": "Simply Schedule Appointments for WordPress through version 1.6.12.32 may expose appointment records to unauthenticated requests. An attacker who can reach the affected REST interface may obtain customer personal data and appointment tokens, and those tokens may allow appointment deletion without logging in.",
  "mitigation": "Disable the plugin or restrict unauthenticated access to its appointment REST endpoints until the vendor provides an update. Where removal is not immediately possible, use a reverse proxy or WAF rule to block unauthenticated requests to the affected appointment API path.",
  "vendor": "croixhaug",
  "product": "Simply Schedule Appointments",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 1.6.12.32"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Simply Schedule Appointments",
      "purl": null
    }
  ],
  "cwes": [
    862
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
  "epss_score": 0.0043,
  "epss_percentile": 0.3579,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": false,
  "pipeline_minutes": 20.217603116666666,
  "t0_at": "2026-10-01T03:28:21.953000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-01T04:46:35.662929+00:00",
      "days": 0.054325346400462965,
      "is_lower_bound": false,
      "measured_at": "2026-10-01T03:28:21.953000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-01T03:28:21.953000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-01T03:28:21.953000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-92245"
    }
  }
}

published 2026-10-01 04:26Z
last change 2026-10-21 05:31Z

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.

Protected by reCAPTCHA; the Google Privacy Policy and Terms of Service apply.