Skip to main content
Menu
CVEs

snct-SportEase web privilege escalation in profile setup via class_id

CVE-2026-79751Published , updated

7.6HighCNA
Exploited
No known exploitation
Fix
Fixed in 1.3
Who is exposed
Not reported

Summary

The SportEase web application lets a logged-in user with an incomplete profile remotely make themselves the representative of any one class during first profile setup. That role lets them view the class roster, including email addresses, and change competition-team assignments for that class only.

Written by a model

Original description

SportEase is a web application for managing school sports events, class rosters, and competition teams. Prior to 1.3, an authenticated account with is_profile_complete=false can submit an attacker-selected class_id for any class in the currently active event to PUT /api/user/profile during first profile completion. AuthHandler.UpdateProfile accepts the class without validating the user's legitimate membership and automatically derives and assigns the corresponding {class_name}_rep role while isFirstCompletion is true. The attacker can become representative of one selected class, view roster information including email addresses, and add or remove competition-team assignments. Downstream handlers correctly reject access to other classes, so the impact is bounded to the selected class, but the representative privilege cannot be revoked through the exposed API and requires direct database intervention or another out-of-band remediation method. This issue is fixed in version 1.3.

What to do

Upgrade to a fixed version: 1.3.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-79751 (SportEase profile update permits class representative self-assignment through user-controlled class_id), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-79751 (entry last updated 2026-11-20):
Affected:
- snct-SportEase web: fixed in 1.3
Fixed versions: 1.3.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-79751 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-79751 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/snct-SportEase/web/security/advisories/GHSA-wfpc-5cqg-3x6c
- https://github.com/snct-SportEase/web/commit/7cda90c9100c4d248e355a5c9bad553807a03e3a
- https://github.com/snct-SportEase/web/commit/98884d8c05f1994f8672db0cfc7cd9d8b5459fe1
- https://github.com/snct-SportEase/web/releases/tag/v1.3
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-79751
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-79751"}.

Affected versions

cve.now Index

11Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.6/10CVSS 7.6
  • No patch0/5No signal

What would change the score

  • Would score about 66 if added to CISA KEV
  • Would score about 61 if CISA's SSVC rates exploitation active
  • Would score about 30 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 6

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · snct-SportEase/web · Advisory GHSA-wfpc-5cqg-3x6c
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-79751
RecordNVD · CVE-2026-79751
Other links 3
RepositoryGitHub · snct-SportEase/web · Commit 7cda90c9
RepositoryGitHub · snct-SportEase/web · Commit 98884d8c
RepositoryGitHub · snct-SportEase/web · Release v1.3

Questions about CVE-2026-79751

Is CVE-2026-79751 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-79751?

web: before 1.3.

Source: cve.now feed data

How do I fix CVE-2026-79751?

Upgrade to a fixed version: 1.3.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.