Skip to main content
VulnerabilityPublished

CVE-2026-79751: snct-SportEase web · Improper Privilege Management

Affects snct-SportEase webSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.6 High : upgrade to 1.3 soon.

Data as of 20 Nov 2026, 17:20 UTC

CVSS 3.1 base score
7.6High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.17.6
Patch
Available – fixed in 1.3
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 24 Oct 2026.

What to do

Upgrade snct-SportEase web to 1.3.

Affected software

ProductAffectedFixed in
snct-SportEasewebAffected
  • <1.3
Fixed in
  • 1.3

AI-suggested

Upgrade snct-SportEase web application to version 1.3 or later, where this vulnerability is fixed. Since the representative privilege cannot be revoked via the API, any existing unauthorized assignments require direct database intervention or other out-of-band remediation methods.

Description

CVE-2026-79751 is an improper privilege management vulnerability in snct-SportEase web application versions prior to 1.3. An authenticated user with an incomplete profile can assign themselves as a class representative for any class in the active event by submitting a chosen class_id during profile completion. This grants unauthorized access to view roster details and modify competition-team assignments for that class. The elevated representative role cannot be revoked via the API and requires direct database or out-of-band remediation. The issue is fixed in version 1.3.

References

Community reviews

Loading reviews…