CVE-2026-12593

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

HIGH
8.7
CVSS Score
Published: July 9, 2026 at 12:29 PM UTC
Updated: October 25, 2026 at 05:10 PM UTC
1 product affected across 1 vendorAxivion

Using Axivion by Qt?

Get instant alerts when new vulnerabilities affect Axivion - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.7
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

7.10.0 ≤ v < 7.10.117.11.0 ≤ v < 7.11.77.12.0 ≤ v < 7.12.27.8.5 ≤ v ≤ 7.8.127.9.0 ≤ v < 7.9.137.10.07.11.07.12.07.8.57.9.0
Affected range stops below 7.10.11, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.11.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.12.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.9.13, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.7HIGHTQtC
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-862

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card