Skip to content
Fencer Intel
critical 9.8

CVE-2024-6914 json

Incorrect Authorization in Multiple WSO2 Products via Account Recovery SOAP Admin Service Leading to Account Takeover

published last yr. modified 4mo ago also EUVD-2024-54595

cvss
9.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 55%
public exploits
0
none known

Summary

An incorrect authorization vulnerability exists in multiple WSO2 products due to a business logic flaw in the account recovery-related SOAP admin service. A malicious actor can exploit this vulnerability to reset the password of any user account, leading to a complete account takeover, including accounts with elevated privileges.

This vulnerability is exploitable only through the account recovery SOAP admin services exposed via the "/services" context path in affected products. The impact may be reduced if access to these endpoints has been restricted based on the "Security Guidelines for Production Deployment" by disabling exposure to untrusted networks.

Patch / fix

  • WSO2 WSO2 API Manager 2.2.0.55, 2.5.0.82, 2.6.0.141, 3.0.0.161, 3.1.0.292, 3.2.0.382, 3.2.1.14, 4.0.0.304, 4.1.0.164, 4.2.0.99, 4.3.0.15
  • WSO2 WSO2 Governance Registry 5.4.0.14
  • WSO2 WSO2 Identity Server 5.3.0.31, 5.4.0.30, 5.4.1.35, 5.5.0.48, 5.6.0.56, 5.7.0.122, 5.8.0.104, 5.9.0.155, 5.10.0.317, 5.11.0.363, 6.0.0.207, 6.1.0.184, 7.0.0.56
  • WSO2 WSO2 Identity Server as Key Manager 5.3.0.36, 5.5.0.49, 5.6.0.70, 5.7.0.121, 5.9.0.162, 5.10.0.311
  • WSO2 WSO2 IoT 3.3.0.59, 3.3.1.61
  • WSO2 WSO2 Open Banking AM 1.3.0.130, 1.4.0.133, 1.5.0.135, 2.0.0.341
  • WSO2 WSO2 Open banking KM 1.3.0.113, 1.4.0.129, 1.5.0.119
  • WSO2 WSO2 Open Banking IAM 2.0.0.362
  • WSO2 WSO2 Carbon Identity Management 5.7.5.9, 5.10.86.4, 5.10.112.14, 5.11.148.13, 5.11.256.15, 5.12.153.58, 5.12.387.41, 5.14.97.75, 5.17.5.282, 5.17.118.4, 5.18.187.265, 5.18.248.14, 5.23.8.184, 5.24.8.6, 5.25.92.92, 5.25.705.6, 7.0.78.32, 7.3.44

Is CVE-2024-6914 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
last yr.

Exploit prediction

0.75% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA 3.1 8.8 CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

  • WSO2 WSO2 API Manager
  • WSO2 WSO2 Governance Registry
  • WSO2 WSO2 Identity Server
  • WSO2 WSO2 Identity Server as Key Manager
  • WSO2 WSO2 IoT
  • WSO2 WSO2 Open Banking AM
  • WSO2 WSO2 Open banking KM
  • WSO2 WSO2 Open Banking IAM
  • WSO2 WSO2 Carbon Identity Management

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.