Axivion up to 7.12.1 OAuth OIDC Authentication redirect
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 1.34+ |
Summary
A vulnerability, which was classified as problematic, has been found in Axivion up to 7.8.12/7.9.12/7.10.10/7.11.6/7.12.1. Affected by this vulnerability is an unknown functionality of the component OAuth OIDC Authentication. This manipulation causes redirect. This vulnerability is registered as CVE-2026-12379. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability was found in Axivion up to 7.8.12/7.9.12/7.10.10/7.11.6/7.12.1. It has been declared as problematic. Affected by this vulnerability is an unknown functionality of the component OAuth OIDC Authentication. The manipulation with an unknown input leads to a redirect vulnerability. The CWE definition for the vulnerability is CWE-601. A web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a Redirect. This simplifies phishing attacks. As an impact it is known to affect integrity. The summary by CVE is:
An Open Redirect vulnerability (CWE-601) exists in the OAuth/OIDC authentication implementation of the Axivion Dashboard. The login flow did not properly restrict the post-authentication redirect to the application's own origin, so a user who follows a crafted login link can be sent to an untrusted external site after authenticating against the genuine Dashboard. Because the link points at the legitimate Dashboard, this can be abused for phishing, for example credential or second-factor theft via a convincing look-alike page. Exploitation requires the victim to follow the attacker-supplied link and complete the authentication flow.
It is possible to read the advisory at wiki.qt.io. This vulnerability is known as CVE-2026-12379 since 06/16/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/16/2026). The attack technique deployed by this issue is T1204.001 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
- 7.8.0
- 7.8.1
- 7.8.2
- 7.8.3
- 7.8.4
- 7.8.5
- 7.8.6
- 7.8.7
- 7.8.8
- 7.8.9
- 7.8.10
- 7.8.11
- 7.8.12
- 7.9.0
- 7.9.1
- 7.9.2
- 7.9.3
- 7.9.4
- 7.9.5
- 7.9.6
- 7.9.7
- 7.9.8
- 7.9.9
- 7.9.10
- 7.9.11
- 7.9.12
- 7.10.0
- 7.10.1
- 7.10.2
- 7.10.3
- 7.10.4
- 7.10.5
- 7.10.6
- 7.10.7
- 7.10.8
- 7.10.9
- 7.10.10
- 7.11.0
- 7.11.1
- 7.11.2
- 7.11.3
- 7.11.4
- 7.11.5
- 7.11.6
- 7.12.0
- 7.12.1
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: RedirectCWE: CWE-601
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
06/16/2026 CVE reserved07/16/2026 Advisory disclosed
07/16/2026 VulDB entry created
07/16/2026 VulDB entry last update
Sources
Advisory: wiki.qt.ioStatus: Confirmed
CVE: CVE-2026-12379 (🔒)
GCVE (CVE): GCVE-0-2026-12379
GCVE (VulDB): GCVE-100-379555
Entry
Created: 07/16/2026 18:10Changes: 07/16/2026 18:10 (51)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.