Description
The implementation of an internal and undocumented Dashboard API endpoint (POST /api/users/~/{user}/tokens) forgot to ensure an HTTP request for creating an API Token for another user had sufficient permission to do so.





Precondition for successful exploitation was a preexisting internal user (with more privileges than the attacker), the attacker knowing its login name and the attacker being able to authenticate to the Dashboard via OAuth/OIDC. The attacker would then have had to forge a token creation API request on behalf of the other user and could have authenticated and finalized the token creation with their own OAuth/OIDC credentials. In the worst case, this would mean an attacker could have become Dashboard Administrator and been able to perform all administrative actions if the preexisting internal user had administrative privileges. In combination with a separate weakness, this could have further led to code execution on the host system running the Dashboard with the privileges of the OS-User running the Dashboard server.
Published: 2026-07-09
Score: 8.7 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability, classified as CWE-862, has a CVSS score of 8.7, indicating high severity. It allows an attacker to create an API token on behalf of another user because the internal POST /api/users/~/{user}/tokens endpoint fails to verify that the requesting user has permission to create tokens for that target user. This omission enables privilege escalation: an attacker who can authenticate to the Dashboard using OAuth/OIDC and who knows the login name of a more‑privileged internal user could create a token for that user, gain that user’s OAuth/OIDC credentials, and, if the target user was an administrator, obtain full administrative control of the Dashboard. In some configurations, combined with other weaknesses, the attacker could further elevate to code execution on the host system under the OS‑user running the Dashboard server.

Affected Systems

The affected product is the Axivion Dashboard from Qt Axivion. All releases before the following fixed versions are vulnerable: 7.9.13, 7.10.11, 7.11.7, and 7.12.2. Deployments running any 7.8.x release from 7.8.5 through 7.8.12 lack a fix, so they must migrate to one of the fixed releases to protect the system.

Risk and Exploitability

The CVSS score is 8.7, indicating high severity, and the EPSS score is <1%, suggesting a low probability of exploitation. The vulnerability is not listed in the CISA KEV catalog. Exploitation requires an existing internal user with higher privileges, knowledge of that user’s login name, and the ability to authenticate to the Dashboard via OAuth/OIDC. Thus the likely attack vector is through internal or compromised accounts that can authenticate, enabling the attacker to create a token for a privileged user and, if that user is an administrator, gain full administrative control. If combined with other weaknesses, the attacker could also achieve code execution on the host system.

Generated by OpenCVE AI on July 29, 2026 at 12:28 UTC.

Remediation

Vendor Solution

Update to one of the fixed releases: 7.9.13, 7.10.11, 7.11.7, or 7.12.2. There is no fixed release on the 7.8.x branch; deployments running 7.8.5-7.8.12 must migrate to one of the fixed releases.


Vendor Workaround

Disable the OIDC/OAuth2/SSO authentication feature or shut down the Dashboard server.


OpenCVE Recommended Actions

  • Apply the vendor patch or upgrade to a fixed release (7.9.13, 7.10.11, 7.11.7, or 7.12.2) which fixes the missing authorization check in the token creation endpoint (CWE-862).
  • Disable the OIDC/OAuth2/SSO authentication feature or shut down the Dashboard server until the patch is applied.
  • Monitor API token creation activity and audit to detect any attempted exploitation.

Generated by OpenCVE AI on July 29, 2026 at 12:28 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 09 Jul 2026 16:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Thu, 09 Jul 2026 13:30:00 +0000

Type Values Removed Values Added
Description The implementation of an internal and undocumented Dashboard API endpoint (POST /api/users/~/{user}/tokens) forgot to ensure an HTTP request for creating an API Token for another user had sufficient permission to do so. Precondition for successful exploitation was a preexisting internal user (with more privileges than the attacker), the attacker knowing its login name and the attacker being able to authenticate to the Dashboard via OAuth/OIDC. The attacker would then have had to forge a token creation API request on behalf of the other user and could have authenticated and finalized the token creation with their own OAuth/OIDC credentials. In the worst case, this would mean an attacker could have become Dashboard Administrator and been able to perform all administrative actions if the preexisting internal user had administrative privileges. In combination with a separate weakness, this could have further led to code execution on the host system running the Dashboard with the privileges of the OS-User running the Dashboard server.
Title Privilege escalation via forged API token creation in Axivion Dashboard OIDC/OAuth2/SSO subsystem
First Time appeared Qt
Qt axivion
Weaknesses CWE-862
CPEs cpe:2.3:a:qt:axivion:*:*:*:*:*:*:*:*
Vendors & Products Qt
Qt axivion
References
Metrics cvssV4_0

{'score': 8.7, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L'}


cve-icon MITRE

Status: PUBLISHED

Assigner: TQtC

Published:

Updated: 2026-07-09T14:20:19.757Z

Reserved: 2026-06-18T09:26:17.599Z

Link: CVE-2026-12593

cve-icon Vulnrichment

Updated: 2026-07-09T14:20:15.130Z

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-07-29T12:30:03Z

Weaknesses