/

CVE-2026-90856

Severity:

HIGH RISK

(7.3)

Improper Privilege Management (CWE-266) in College Signup Flow

CVE-2026-90856

Deferred

Vulnerability type

Category:

Improper Privilege Management

CWE:

CWE-266, CWE-269

Impact:

Unauthorized Privilege Escalation

Severity:

HIGH RISK

(7.3)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A high-severity privilege management vulnerability in the College Notes Gallery Management System allows the registration flow to improperly process the user-supplied role argument. A remote, potentially unauthenticated attacker may exploit this behavior to obtain unauthorized privileges when registration input is accepted without enforcing a trusted server-side role policy.

Affected context

The issue occurs in the application's signup.php registration flow, where the role argument can influence account privilege assignment. Deployments may be exposed when registration is remotely accessible and role values are accepted from client-controlled input without strict authorization checks or a secure default role.

Exploit preconditions

  • Attack surface: Remote registration endpoint
  • Required access: Access to submit registration requests; authentication may not be required
  • Trigger point: Processing of the role argument in signup.php
  • Why exploitation is possible: The application may trust a client-controlled role value instead of assigning privileges exclusively through trusted server-side logic

Why this happens

The underlying bug is improper privilege management: a security-sensitive authorization attribute is exposed to an untrusted request and is not sufficiently constrained before account creation.

This maps primarily to CWE-266: Incorrect Privilege Assignment, with a related association to CWE-269: Improper Privilege Management. The insecure pattern is allowing registration data to determine authorization state without enforcing a fixed low-privilege default and separate administrative approval or provisioning controls.

Potential impact

  • An attacker may create an account with unauthorized privileges
  • Unauthorized users could access restricted application functions
  • Attackers could modify, delete, or disclose protected records
  • The application could experience administrative account compromise or integrity loss

General mitigation guidance

Mitigation generally focuses on removing privilege decisions from client-controlled registration data.

Common defensive patterns include:

  • Assigning every newly registered account a fixed least-privilege role server-side
  • Ignoring or rejecting client-supplied administrative role fields
  • Requiring separate trusted workflows for elevated-role assignment
  • Enforcing authorization checks on every protected operation
  • Applying deny-by-default access control and least privilege
  • Auditing role changes and alerting on unexpected privilege assignments
  • Validating input against an allowlist without treating validation as a substitute for authorization

How teams detect issues like this

Organizations can identify similar issues through:

  • Static analysis rules that flag request parameters used in role or permission assignment
  • Code review checks for client-controlled authorization fields in registration and profile-update handlers
  • Tests that attempt to submit elevated role values during account creation
  • Policy enforcement requiring server-side defaults for security-sensitive attributes
  • Audit-log monitoring for unexpected role assignments or privilege changes

Automated security review tools may help identify data flows from HTTP parameters into authorization decisions.

Sources

SourceLink
github.comgithub.com/Andyov0/cve/issues/4
vuldb.comvuldb.com/cve/CVE-2026-90856
vuldb.comvuldb.com/submit/927252
vuldb.comvuldb.com/vuln/403413
vuldb.comvuldb.com/vuln/403413/cti
sourcecodester.comsourcecodester.com/

Frequently asked

questions

Yes. The disclosed issue affects a remotely reachable registration flow, although actual exposure depends on deployment configuration and whether registration is enabled.

Not necessarily. If the registration endpoint accepts requests without authentication, an attacker may be able to attempt exploitation before account creation.

Assign a fixed low-privilege role on the server for new accounts and move elevated-role assignment into a separate trusted administrative workflow.

Treat roles and permissions as security-sensitive server-side state, enforce authorization on every protected action, use least privilege, and test registration endpoints with unexpected and elevated role values.

Find out what's already
exploitable in your codebase.