CVE-2026-117028

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

GHSA-w3xr-5cfx-cw4p ↗EUVD-2026-113992 ↗

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.
Skuul School Management System n/a
ETK-2026-3138Zero's internal tracking ID, independent of the CVE number., permanent identifier
2h 02msince last run
50mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+27h01m
0
+2h
+4h
+6h
+8h
+10h

description

Skuul School Management System through version 2.6.5 does not adequately enforce ownership checks when students view examination results. An authenticated student may access another student's results and marks. Access requires a valid student account.

mitigation

Restrict student access to result-viewing functions where possible, and enforce server-side checks that the requested record belongs to the logged-in student. Monitor result-access logs for cross-student access and apply a vendor update when one is published.

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.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
50m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-30 00:00Z
Δ 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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-10-30 00:00Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3138",
  "cve_id": "CVE-2026-117028",
  "display_id": "CVE-2026-117028",
  "ghsa_id": "GHSA-w3xr-5cfx-cw4p",
  "euvd_id": "EUVD-2026-113992",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Improper authorization in Skuul School Management System",
  "summary": "Skuul School Management System through version 2.6.5 does not adequately enforce ownership checks when students view examination results. An authenticated student may access another student's results and marks. Access requires a valid student account.",
  "mitigation": "Restrict student access to result-viewing functions where possible, and enforce server-side checks that the requested record belongs to the logged-in student. Monitor result-access logs for cross-student access and apply a vendor update when one is published.",
  "vendor": null,
  "product": "Skuul School Management System",
  "affected": [
    {
      "affected_notes": [
        "n/a"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "n/a",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 49.84962695,
  "t0_at": "2026-10-30T00:00:00+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-30T00:00:00+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-30T00:00:00+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-117028"
    }
  }
}

published 2026-10-31 02:11Z
last change 2026-10-31 04:46Z

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.