/

CVE-2026-90523

Severity:

HIGH RISK

(7.3)

Improper Privilege Management (CWE-266) in Tourism System

CVE-2026-90523

Deferred

Vulnerability type

Category:

Improper Privilege Management

CWE:

CWE-266, CWE-269

Impact:

Unauthorized Privilege Assignment

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 improper privilege management vulnerability affects the User Register Endpoint in jaychouchannel Tourism-Management-System. Remote attackers may manipulate user-related input, potentially causing accounts or actions to receive privileges beyond those intended by the application.

Affected context

The issue occurs in the user registration flow implemented by UsersController.java, where the UsersEntity argument can be manipulated. Risk is greater when registration data is accepted remotely and the application derives authorization-relevant attributes from client-controlled input without enforcing server-side privilege boundaries.

Exploit preconditions

  • Attack surface: Public or remotely reachable user registration endpoint
  • Required access: Network access to submit registration requests; valid authentication may not be required
  • Trigger point: Processing of attacker-controlled UsersEntity data during account creation
  • Why exploitation is possible: Authorization-relevant values may be accepted or handled without sufficient server-side restriction, allowing an account to obtain privileges beyond the intended registration role

Why this happens

The underlying bug is improper privilege management, mapped primarily to CWE-266 and related to CWE-269: Improper Privilege Management. The insecure pattern occurs when a registration handler trusts client-supplied entity fields or fails to establish privileged attributes from a server-controlled policy. As a result, identity creation and authorization decisions can become coupled to attacker-controlled input.

Potential impact

  • An attacker may create an account with unauthorized privileges
  • Unauthorized users could access administrative or restricted functionality
  • Application data could be modified, disclosed, or deleted
  • A compromised account could enable further lateral movement within the application

General mitigation guidance

Mitigation generally focuses on making privilege assignment server-controlled and separating account creation from authorization decisions.

Common defensive patterns include:

  • Assigning new accounts the least-privileged role by default
  • Ignoring or overriding client-supplied administrative and authorization fields
  • Enforcing authorization checks on every privileged operation
  • Applying allowlisted role transitions through controlled administrative workflows
  • Validating identity attributes independently of request-body entity binding
  • Limiting account-management permissions and protecting administrative endpoints

How teams detect issues like this

Detection approaches can include:

  • Static analysis for direct binding of request objects to authorization-sensitive entities
  • Code review checks for client-controlled role, permission, group, or status fields
  • Tests that attempt to register accounts with elevated authorization attributes
  • Monitoring for unusual privileged-account creation and unexpected role changes
  • Policy enforcement requiring server-side authorization decisions for registration and account updates

Automated security review tools may help identify unsafe entity binding and missing authorization checks.

Sources

SourceLink
github.comgithub.com/jaychouchannel/Tourism-Management-System/
github.comgithub.com/jaychouchannel/Tourism-Management-System/commit/84d8ec384f669df3985293dab293bb7b477efa64
github.comgithub.com/jaychouchannel/Tourism-Management-System/issues/10
vuldb.comvuldb.com/cve/CVE-2026-90523
vuldb.comvuldb.com/submit/912244
vuldb.comvuldb.com/vuln/403113
vuldb.comvuldb.com/vuln/403113/cti

Frequently asked

questions

Yes. The described attack surface is the remotely accessible User Register Endpoint, although exposure depends on how the application is deployed and whether the endpoint is reachable.

Not necessarily. Because the affected function is associated with registration, an attacker may only need the ability to submit registration requests, subject to deployment-specific controls.

Ensure that privilege and role attributes are assigned exclusively by trusted server-side logic, with new accounts receiving the minimum required permissions.

Use strict allowlists for registration fields, avoid binding client input directly to authorization-sensitive entities, test privilege boundaries, and continuously monitor privileged-account creation and role changes.

Find out what's already
exploitable in your codebase.