Privilege escalation via forged API token creation in Axivion Dashboard OIDC/OAuth2/SSO subsystem

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.

Scores

EPSS (exploitation in 30 days)

0.43% · top 62% of all CVEs (6 Nov 2026)

CISA SSVC

Exploitation: none · Automatable: no · Technical impact: total

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.7.

Weakness

• CWE-862 Missing Authorization (opens in a new tab)All about CWE-862 and its CVEs

Affected products

• Qt · Axivion

  • affected 7.8.5 – ≤ 7.8.12
  • affected 7.9.0 – < 7.9.13
  • affected 7.10.0 – < 7.10.11
  • affected 7.11.0 – < 7.11.7
  • affected 7.12.0 – < 7.12.2

What to do

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.

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

References (1)

• Qt Group Internal Vulnerability Ticket (opens in a new tab)issue-tracking

Sources

The same CVE in the primary databases and aggregators, to check against.

• CVE.org record (opens in a new tab)
• CVE List JSON (GitHub) (opens in a new tab)
• NVD (opens in a new tab)
• FIRST EPSS (opens in a new tab)
• OSV.dev (opens in a new tab)
• GitHub Advisories (opens in a new tab)
• CIRCL Vulnerability-Lookup (opens in a new tab)

Badge for a README or a ticket

[![CVE-2026-12593](https://trackcve.app/badge/CVE-2026-12593.svg)](https://trackcve.app/cve/CVE-2026-12593)

Record last updated 9 Jul 2026, 14:20 UTC.