{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-12593 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-12593 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-12593 is a high-severity missing authorization vulnerability in Qt Axivion, published on 9 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-12593 and fix it if it is affected.\n\nWhat it is: CVE-2026-12593 is a high-severity missing authorization vulnerability in Qt Axivion, published on 9 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-12593 in the wild and no public exploit code.\n\nAffected product: Qt Axivion. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-12593/ (Markdown: https://insights.sbomify.com/CVE-2026-12593/index.md)","id":"CVE-2026-12593","markdown":"https://insights.sbomify.com/CVE-2026-12593/index.md","name":"CVE-2026-12593","record":{"aliases":["GHSA-2f7g-h2w3-wgvx"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["privilege_escalation","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Axivion Dashboard","requires_auth":"low_privilege","summary":"Attackers can forge API tokens for other users to escalate privileges to Administrator, potentially leading to code execution on the host system.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"TQtC","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","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","version":"4.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"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.\n\nPrecondition 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Privilege escalation via forged API token creation in Axivion Dashboard OIDC/OAuth2/SSO subsystem","id":"CVE-2026-12593","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"LoginPress Pro \u003c= 6.2.3 - Unauthenticated Authentication Bypass via Unverified OAuth Email via Discord OAuth Callback","id":"CVE-2026-12595"},"packages":[],"prev":{"headline":"SlimStat Analytics \u003c 5.5.0 - Unauthenticated Stored XSS via CF-IPCountry Header","id":"CVE-2026-12592"},"products":["Axivion"],"published":"2026-07-09","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-09","vendors":["Qt"]},"summary":"Attackers can forge API tokens for other users to escalate privileges to Administrator, potentially leading to code execution on the host system.","url":"https://insights.sbomify.com/CVE-2026-12593/"}