/

CVE-2026-51119

Severity:

CRITICAL RISK

(9.1)

Privilege Escalation (CWE-269) in Invixium IXM WEB

CVE-2026-51119

Deferred

Vulnerability type

Category:

Privilege Escalation

CWE:

CWE-269

Impact:

Elevation of Privilege

Severity:

CRITICAL RISK

(9.1)

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 privilege escalation flaw in Invixium IXM WEB allows attackers to gain higher-level access through the /SystemUsers/CreateAppUser components.

When user creation and role assignment are not properly enforced, an attacker may create or modify application accounts with elevated privileges, leading to full administrative control of the system.

Affected context

This vulnerability occurs within the account and role management functionality of Invixium IXM WEB, specifically in the /SystemUsers/CreateAppUser components.

It is relevant in deployments where application users can invoke this endpoint and where server-side checks on role assignment, authorization, or ownership are incomplete or inconsistently enforced.

The issue is most pronounced when access control logic relies on client-supplied parameters or assumes that only trusted administrators will reach the user creation flow without verifying that assumption.

Exploit preconditions

  • Attack surface: Web application interface, exposed via HTTP(S) endpoints tied to user and role management.
  • Required access: Ability to reach and interact with /SystemUsers/CreateAppUser (e.g., as a normal or low-privileged user, or via a compromised account).
  • Trigger point: Submission of crafted requests that create or modify application users while specifying elevated roles or permissions.
  • Why exploitation is possible: Server-side authorization checks on role assignment and user creation are insufficient or missing, allowing client-controlled parameters to influence privilege levels without proper validation against the caller's actual permissions.

Why this happens

This vulnerability stems from improper privilege management and incomplete enforcement of authorization policies for user and role creation.

The /SystemUsers/CreateAppUser components appear to trust incoming role or privilege-related data and fail to ensure that the caller is authorized to assign or obtain those higher privileges.

Conceptually, this maps to CWE-269: Improper Privilege Management, where the system does not correctly distinguish or constrain the actions of lower-privileged users, allowing them to perform administrative operations or escalate their own privileges.

Potential impact

  • Attackers may gain administrative access to the Invixium IXM WEB application.
  • Malicious users could create backdoor accounts with persistent elevated privileges.
  • Critical configuration, user data, and access logs can be altered or deleted.
  • Access control policies and biometric or access-control records may be tampered with.
  • The broader environment integrated with IXM WEB (e.g., physical access systems) could be indirectly compromised.

General mitigation guidance

Mitigation generally focuses on hardening authorization logic around user and role management and ensuring privileges are never derived from untrusted input.

Common defensive patterns include:

  • Enforcing strict server-side authorization checks on all operations that create, modify, or assign roles to users, based solely on the authenticated caller's permissions.
  • Centralizing role and privilege definitions and validating that only designated administrative roles can assign or alter high-impact privileges.
  • Avoiding reliance on client-supplied role identifiers or flags; treat all such data as untrusted and re-derive effective privileges on the server.
  • Applying least-privilege design so everyday user accounts cannot access user management endpoints or sensitive configuration areas.
  • Logging and monitoring all administrative actions, including account creation and role changes, and regularly reviewing for anomalies.

How teams detect issues like this

Detecting this class of issue typically involves:

  • Code review focused on authorization checks for user creation, role assignment, and any endpoint under /SystemUsers, verifying that access decisions are enforced server-side.
  • Static analysis rules that flag direct use of client-supplied role or permission parameters without privilege validation against the authenticated user.
  • Security testing and automated integration tests that attempt to perform administrative actions (e.g., creating admin users) from low-privileged accounts.
  • Policy-based enforcement requiring all sensitive endpoints (user management, configuration changes) to include explicit authorization checks tied to well-defined roles.
  • Runtime monitoring for suspicious patterns such as frequent creation of privileged accounts or role changes initiated by non-administrative users.

Sources

SourceLink
affected.comaffected.com
invixium.cominvixium.com
github.comgithub.com/A17-ba/CVE-2026-51119
invixium.cominvixium.com

Frequently asked

questions

Exploitability depends on who can reach the /SystemUsers/CreateAppUser components. If regular or lightly privileged users can call this functionality, the issue can be widely exploitable; if access is already narrowly restricted, the risk is concentrated around those accounts.

An attacker typically needs at least the ability to authenticate or otherwise send requests to the affected endpoint. Once they can do so, insufficient authorization checks may allow them to create or elevate accounts to administrative levels.

The most robust fix is to enforce centralized, server-side authorization checks on every user and role management operation, ensuring that only trusted administrative roles can create, modify, or assign high-privilege accounts. Client-provided role or privilege information should never be accepted without validation.

Future designs should adopt least-privilege principles, treat all client inputs as untrusted, and implement a consistent authorization framework around sensitive functions. Regular security reviews, automated tests for access control boundaries, and monitoring of administrative actions help catch regressions early and prevent privilege escalation vulnerabilities.

Find out what's already
exploitable in your codebase.