← back to feed
CVE-2026-104766

CVE-2026-104766

validatedZero produced an exploit or a check.

GHSA-h977-fppf-xgg7 ↗EUVD-2026-96090 ↗

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.3
CWE-269 Improper Privilege Management
ETK-2026-1138Zero's internal tracking ID, independent of the CVE number., permanent identifier
cvss8.8cna vendorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
+1h18mTTV
59mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0mcheck available+78magent stopped
0
+15min
+30min
+45min
+60min

description

LatePoint for WordPress versions through 5.7.3 allow improperly authorized settings changes that can alter the WordPress role assigned to newly created LatePoint customers. An authenticated user with a LatePoint role granted settings__edit can cause a later customer registration to receive administrator access. Exploitation depends on that capability having been delegated and on customer self-registration being available.

mitigation

Remove settings__edit from LatePoint agent and custom roles, and restrict or disable LatePoint customer self-registration where feasible. Apply a vendor update when one is available; no fixed version is recorded.

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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.30%21st percentile
agent run time
59m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-10 05:30Z
Δ 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-10 05:30Z
    cve_org: trigger signal, started the run
    https://www.cve.org/CVERecord?id=CVE-2026-104766

this entry in the feed

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

{
  "etk_id": "ETK-2026-1138",
  "cve_id": "CVE-2026-104766",
  "display_id": "CVE-2026-104766",
  "ghsa_id": "GHSA-h977-fppf-xgg7",
  "euvd_id": "EUVD-2026-96090",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Privilege escalation in the LatePoint WordPress plugin",
  "summary": "LatePoint for WordPress versions through 5.7.3 allow improperly authorized settings changes that can alter the WordPress role assigned to newly created LatePoint customers. An authenticated user with a LatePoint role granted settings__edit can cause a later customer registration to receive administrator access. Exploitation depends on that capability having been delegated and on customer self-registration being available.",
  "mitigation": "Remove settings__edit from LatePoint agent and custom roles, and restrict or disable LatePoint customer self-registration where feasible. Apply a vendor update when one is available; no fixed version is recorded.",
  "vendor": "latepoint",
  "product": "Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 5.7.3"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress",
      "purl": null
    }
  ],
  "cwes": [
    269
  ],
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.003,
  "epss_percentile": 0.2158,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": false,
  "pipeline_minutes": 58.56033298333333,
  "t0_at": "2026-10-10T05:30:57.307000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-10T06:48:40.084024+00:00",
      "days": 0.05396732666666667,
      "is_lower_bound": false,
      "measured_at": "2026-10-10T05:30:57.307000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-10T05:30:57.307000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-10T05:30:57.307000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-104766"
    }
  }
}

published 2026-10-10 05:50Z
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.

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