dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2026-51119

CRITICAL · 9.1 CVSS v3.1 Published 2026-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An issue in Invixium IXM WEB v.2.3.85.25 allows an attacker to escalate privileges via the /SystemUsers/CreateAppUser components

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Invixium IXM WEB version 2.3.85.25 contains a privilege escalation vulnerability in the /SystemUsers/CreateAppUser endpoint that allows authenticated or unauthenticated attackers to create administrative users without proper authorization, bypassing role-based access controls.

MitigationApply vendor-provided patches for IXM WEB v2.3.85.25. If no patch exists, implement proper authorization checks on the CreateAppUser endpoint to enforce role-based access control and validate user permissions before user creation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed IXM WEB version
    Access the IXM WEB administration interface and navigate to System > About or Help > About to view the software version. Alternatively, check the HTTP response headers or login page source for version information.
    Affected if The installed version is 2.3.85.25 exactly, or if the version cannot be definitively determined but the software is confirmed to be Invixium IXM WEB.
  2. Confirm /SystemUsers/CreateAppUser endpoint exists
    Send an HTTP GET or POST request to https://[target]/SystemUsers/CreateAppUser and observe the response. A 200 OK or 403 response indicates the endpoint exists and is reachable.
    Affected if The endpoint responds (any status code other than 404 Not Found), indicating the vulnerable component is present.
  3. Test endpoint access control with low-privilege account
    Log in with a non-administrator user account (or create one if necessary) and attempt to access or send a request to /SystemUsers/CreateAppUser. Capture the HTTP response code and any error messages.
    Affected if The low-privileged user receives a successful response (200 OK) or is able to interact with the endpoint without receiving an authorization error.
  4. Review existing user accounts for unauthorized admins
    Using an administrator account, navigate to System > Users or SystemUsers list and examine all accounts with Administrator privileges. Look for accounts that were not created by known administrators or that appear suspicious.
    Affected if There are administrative accounts that were not created by known, authorized administrators, or there are more admin accounts than expected.
  5. Check application logs for CreateAppUser activity
    Access IXM WEB logs (typically in System > Logs or via log files on the server) and search for entries related to /SystemUsers/CreateAppUser or user creation events. Look for creation timestamps and the originating user account.
    Affected if Log entries show CreateAppUser calls from accounts that should not have administrative privileges.

If running Invixium IXM WEB version 2.3.85.25 (or an indeterminate version) AND the /SystemUsers/CreateAppUser endpoint is accessible to non-administrative users, the environment is affected by this privilege escalation vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-provided patches for IXM WEB v2.3.85.25. If no patch exists, implement proper authorization checks on the CreateAppUser endpoint to enforce role-based access control and validate user permissions before user creation.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-51119 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-51119 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data