Skip to main content
Vulnerability Database/CVE-2026-100878

CVE-2026-100878: StarTraining Auth Bypass Vulnerability

CVE-2026-100878 is an authorization bypass flaw in zhistaredu StarTraining up to version 3.8.1 that allows remote attackers to escalate privileges. This post explains its technical details, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-100878 Overview

CVE-2026-100878 is an authorization bypass vulnerability in zhistaredu StarTraining versions up to 3.8.1. The flaw resides in the SysUser.isAdmin function within edu-common/src/main/java/com/edu/common/core/domain/entity/SysUser.java, exposed through the authRole endpoint. Attackers can manipulate the userId or roleIds parameters to bypass authorization checks and elevate privileges. The weakness is categorized under CWE-285 (Improper Authorization). Remote exploitation is possible with low privileges, and a public proof-of-concept exists. The vendor was contacted but did not respond to the disclosure.

Critical Impact

Authenticated remote attackers can bypass role-based access controls to perform privileged administrative actions in StarTraining instances.

Affected Products

  • zhistaredu StarTraining versions up to and including 3.8.1
  • Component: authRole endpoint
  • Source file: edu-common/src/main/java/com/edu/common/core/domain/entity/SysUser.java

Discovery Timeline

  • 2026-09-27 - CVE-2026-100878 published to NVD
  • 2026-09-28 - Last updated in NVD database

Technical Details for CVE-2026-100878

Vulnerability Analysis

The vulnerability resides in the authorization logic exposed through the StarTraining authRole endpoint. The SysUser.isAdmin function determines administrative status based on user-supplied identifiers rather than enforcing server-side session context. Because the endpoint trusts attacker-controlled userId and roleIds inputs, a low-privileged authenticated user can request role assignments that should be reserved for administrators. The result is an Insecure Direct Object Reference leading to privilege escalation within the application.

An EPSS score of 0.211% places near-term exploitation probability in the lower range, however a public proof-of-concept is referenced in the GitHub advisory, which increases the risk of opportunistic abuse.

Root Cause

The root cause is improper authorization in the authRole request flow. The application performs role assignment operations without validating that the authenticated principal has the authority to modify the target user or assign the requested role identifiers. Access control decisions are driven by client-supplied data rather than a server-side authorization check tied to the session identity.

Attack Vector

An authenticated attacker sends a crafted request to the authRole endpoint, supplying a userId corresponding to a target account and roleIds referencing elevated roles. Because the SysUser.isAdmin logic can be influenced through this parameter manipulation, the server grants the requested role mapping. The attack originates over the network and does not require user interaction. See the GitHub Security Advisory for exploitation details.

No verified exploit code is reproduced here. Refer to the published advisory for request structure and payload specifics.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-100878

Indicators of Compromise

  • HTTP requests to the authRole endpoint originating from non-administrative user sessions.
  • Role assignment events where the acting principal lacks administrative privileges in audit logs.
  • Unexpected changes to sys_user_role or equivalent persistence tables mapping users to elevated roles.
  • New administrator-equivalent accounts appearing without a corresponding administrative action record.

Detection Strategies

  • Instrument application-layer logging on the authRole endpoint to capture requester identity, target userId, and submitted roleIds values.
  • Correlate role modification events with the session identity performing them and alert on privilege elevation by non-admin principals.
  • Baseline the normal set of users who perform role management and alert on deviations.

Monitoring Recommendations

  • Enable database audit logging on role and permission tables within the StarTraining schema.
  • Forward StarTraining application logs to a centralized SIEM for retrospective analysis and alerting.
  • Review authentication logs for repeated access to administrative endpoints by low-privileged accounts.

How to Mitigate CVE-2026-100878

Immediate Actions Required

  • Restrict network access to StarTraining administrative endpoints using reverse proxy or WAF rules until a vendor patch is available.
  • Audit all current sys_user_role mappings for unauthorized role assignments and revert anomalies.
  • Rotate credentials for any accounts suspected of being compromised or elevated.
  • Monitor the GitHub Security Advisory and the VulDB entry for vendor updates.

Patch Information

As of the published advisory, the vendor has not responded to disclosure and no official patch has been released. Organizations running StarTraining versions up to 3.8.1 should treat this as an unpatched vulnerability and apply compensating controls.

Workarounds

  • Place the authRole endpoint behind a web application firewall rule that validates the requester holds an administrative session.
  • Implement a server-side authorization filter that cross-checks the acting session's role before processing any userId or roleIds modification.
  • Limit application access to trusted internal networks or VPN-restricted segments where feasible.
  • Enforce short session lifetimes and mandatory multi-factor authentication to reduce the window for abuse.
bash
# Example reverse-proxy rule (nginx) restricting authRole to admin source IPs
location /authRole {
    allow 10.0.0.0/24;   # admin management subnet
    deny all;
    proxy_pass http://startraining_backend;
}

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.