← back to feed
CVE-2026-110653

CVE-2026-110653

validatedZero produced an exploit or a check.

GHSA-3xwr-ghgc-2994 ↗EUVD-2026-103217 ↗

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.
latepoint Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress <= 5.7.4
CWE-287 Improper Authentication
ETK-2026-1835Zero's internal tracking ID, independent of the CVE number., permanent identifier
cvss9.1cna vendorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
+57mTTV
28mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0mcheck available+57magent stopped
0
+15min
+30min
+45min
+60min

description

LatePoint for WordPress through version 5.7.4 does not safely enforce limits on concurrent OTP verification attempts. An unauthenticated attacker who knows a customer's registered email address or phone number may bypass the attempt limit and access that customer's account.

mitigation

Disable or restrict public OTP-based customer authentication where operationally feasible until the vendor provides a corrected release. Monitor OTP verification activity and protect customer accounts with additional authentication controls.

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.40%33rd percentile
agent run time
28m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-17 02:31Z
Δ 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-17 02:31Z
    cve_org: trigger signal, started the run
    https://www.cve.org/CVERecord?id=CVE-2026-110653

this entry in the feed

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

{
  "etk_id": "ETK-2026-1835",
  "cve_id": "CVE-2026-110653",
  "display_id": "CVE-2026-110653",
  "ghsa_id": "GHSA-3xwr-ghgc-2994",
  "euvd_id": "EUVD-2026-103217",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Race-condition authentication bypass in LatePoint for WordPress",
  "summary": "LatePoint for WordPress through version 5.7.4 does not safely enforce limits on concurrent OTP verification attempts. An unauthenticated attacker who knows a customer's registered email address or phone number may bypass the attempt limit and access that customer's account.",
  "mitigation": "Disable or restrict public OTP-based customer authentication where operationally feasible until the vendor provides a corrected release. Monitor OTP verification activity and protect customer accounts with additional authentication controls.",
  "vendor": "latepoint",
  "product": "Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 5.7.4"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress",
      "purl": null
    }
  ],
  "cwes": [
    287
  ],
  "cvss_score": 9.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
  "epss_score": 0.004,
  "epss_percentile": 0.3313,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": false,
  "pipeline_minutes": 28.401460666666665,
  "t0_at": "2026-10-17T02:31:06.697000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-17T03:27:53.219941+00:00",
      "days": 0.03942734885416667,
      "is_lower_bound": false,
      "measured_at": "2026-10-17T02:31:06.697000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-17T02:31:06.697000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-17T02:31:06.697000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-110653"
    }
  }
}

published 2026-10-17 02:59Z
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.