CVE-2026-63244

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

GHSA-6hr5-7mj9-8pm2 ↗EUVD-2026-108611 ↗

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.
WizLearn Technologies Pte. Ltd. Learning-Management-System
ETK-2026-2544Zero's internal tracking ID, independent of the CVE number., permanent identifier
5h 45msince last run
32mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+32h25m
0
+2h
+4h
+6h
+8h
+10h

description

WizLearn Technologies Learning Management System is affected by an authentication bypass. An unauthenticated remote attacker may gain access to user accounts and potentially obtain administrative control; the issue requires sending a specially crafted POST request.

mitigation

No fixed version or specific workaround is supported by the evidence. Restrict external access to the LMS and require network-level access controls until vendor remediation guidance is available.

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.
–
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.
–
agent run time
32m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-23 07:24Z
Δ 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

No artifact: no remotely reachable path found.

source signals

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

  1. 2026-10-23 07:24Z
    ghsa: trigger signal, started the run
  2. 2026-10-23 07:24Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2544",
  "cve_id": "CVE-2026-63244",
  "display_id": "CVE-2026-63244",
  "ghsa_id": "GHSA-6hr5-7mj9-8pm2",
  "euvd_id": "EUVD-2026-108611",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authentication bypass in WizLearn Learning Management System",
  "summary": "WizLearn Technologies Learning Management System is affected by an authentication bypass. An unauthenticated remote attacker may gain access to user accounts and potentially obtain administrative control; the issue requires sending a specially crafted POST request.",
  "mitigation": "No fixed version or specific workaround is supported by the evidence. Restrict external access to the LMS and require network-level access controls until vendor remediation guidance is available.",
  "vendor": "WizLearn Technologies Pte. Ltd.",
  "product": "Learning-Management-System",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Learning Management System",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 9.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": null,
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 32.13895658333333,
  "t0_at": "2026-10-23T07:24:30.089000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-23T07:24:30.089000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-23T07:24:30.089000+00:00",
      "url": "https://github.com/advisories/GHSA-6hr5-7mj9-8pm2"
    }
  }
}

published 2026-10-24 15:17Z
last change 2026-10-24 20:19Z

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.