CVE-2026-108951

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

GHSA-pj48-vpfx-3cj9 ↗EUVD-2026-97358 ↗

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.
lavalite cms <= 10.1.2
CWE-863 Incorrect Authorization
ETK-2026-1362Zero's internal tracking ID, independent of the CVE number., permanent identifier
8d 14h 19msince last run
1h 01mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+2h16m
0
+4h
+6h
+8h
+10h
+12h

description

LavaLite CMS through 10.1.2 is affected by an authorization bypass in user account updates. An authenticated low-privileged user may modify another user’s account details, potentially including an administrator account. Exploitation requires a valid low-privileged account.

mitigation

Restrict access to the affected user-update functionality to trusted administrators and closely review account-change activity. Apply a vendor-provided update when one is available; no fixed version is recorded in the advisory.

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.
contextual
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
1h 01m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-12 12:13Z
Δ 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

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

  1. 2026-10-12 12:13Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1362",
  "cve_id": "CVE-2026-108951",
  "display_id": "CVE-2026-108951",
  "ghsa_id": "GHSA-pj48-vpfx-3cj9",
  "euvd_id": "EUVD-2026-97358",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authorization bypass in LavaLite CMS user updates",
  "summary": "LavaLite CMS through 10.1.2 is affected by an authorization bypass in user account updates. An authenticated low-privileged user may modify another user’s account details, potentially including an administrator account. Exploitation requires a valid low-privileged account.",
  "mitigation": "Restrict access to the affected user-update functionality to trusted administrators and closely review account-change activity. Apply a vendor-provided update when one is available; no fixed version is recorded in the advisory.",
  "vendor": "lavalite",
  "product": "cms",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 10.1.2"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "cms",
      "purl": null
    }
  ],
  "cwes": [
    863
  ],
  "cvss_score": 7.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N",
  "epss_score": 0.003,
  "epss_percentile": 0.2155,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 60.549941616666665,
  "t0_at": "2026-10-12T12:13:04.153000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-12T12:13:04.153000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-12T12:13:04.153000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-108951"
    }
  }
}

published 2026-10-12 13:28Z
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.