CVE-2024-6914: Incorrect Authorization in Multiple WSO2 Products via Account Recovery SOAP Admin Service Leading to Account Takeover
Noroxi assessment
Priority: Monitor (action score 39/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.75% (FIRST EPSS); higher than 55.5% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- May 22, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.7% · 55th percentile
- CWE
- CWE-863
Report tools
Action score
39
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · WSO2
- 9.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| wso2 | api manager | cpe:2.3:a:wso2:api_manager |
| wso2 | identity server | cpe:2.3:a:wso2:identity_server |
| wso2 | identity server as key manager | cpe:2.3:a:wso2:identity_server_as_key_manager |
| wso2 | open banking am | cpe:2.3:a:wso2:open_banking_am |
| wso2 | open banking iam | cpe:2.3:a:wso2:open_banking_iam |
| wso2 | open banking km | cpe:2.3:a:wso2:open_banking_km |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (WSO2). Independent of NVD's CPE analysis and usually ahead of it.
WSO2 WSO2 API Manager
- before 2.2.0unknown
- 2.2.0 and later · before 2.2.0.55affected
- 2.5.0 and later · before 2.5.0.82affected
- 2.6.0 and later · before 2.6.0.141affected
- 3.0.0 and later · before 3.0.0.161affected
- 3.1.0 and later · before 3.1.0.292affected
- 3.2.0 and later · before 3.2.0.382affected
- 3.2.1 and later · before 3.2.1.14affected
- 4.0.0 and later · before 4.0.0.304affected
- 4.1.0 and later · before 4.1.0.164affected
WSO2 WSO2 Carbon Identity Management
- 5.7.5 and later · before 5.7.5.9affected
- 5.10.86 and later · before 5.10.86.4affected
- 5.10.112 and later · before 5.10.112.14affected
- 5.11.148 and later · before 5.11.148.13affected
- 5.11.256 and later · before 5.11.256.15affected
- 5.12.153 and later · before 5.12.153.58affected
- 5.12.387 and later · before 5.12.387.41affected
- 5.14.97 and later · before 5.14.97.75affected
- 5.17.5 and later · before 5.17.5.282affected
- 5.17.118 and later · before 5.17.118.4affected
WSO2 WSO2 Governance Registry
- 5.4.0 and later · before 5.4.0.14affected
WSO2 WSO2 Identity Server
- before 5.3.0unknown
- 5.3.0 and later · before 5.3.0.31affected
- 5.4.0 and later · before 5.4.0.30affected
- 5.4.1 and later · before 5.4.1.35affected
- 5.5.0 and later · before 5.5.0.48affected
- 5.6.0 and later · before 5.6.0.56affected
- 5.7.0 and later · before 5.7.0.122affected
- 5.8.0 and later · before 5.8.0.104affected
- 5.9.0 and later · before 5.9.0.155affected
- 5.10.0 and later · before 5.10.0.317affected
WSO2 WSO2 Identity Server as Key Manager
- before 5.3.0unknown
- 5.3.0 and later · before 5.3.0.36affected
- 5.5.0 and later · before 5.5.0.49affected
- 5.6.0 and later · before 5.6.0.70affected
- 5.7.0 and later · before 5.7.0.121affected
- 5.9.0 and later · before 5.9.0.162affected
- 5.10.0 and later · before 5.10.0.311affected
WSO2 WSO2 IoT
- 3.3.0 and later · before 3.3.0.59affected
- 3.3.1 and later · before 3.3.1.61affected
WSO2 WSO2 Open Banking AM
- before 1.3.0unknown
- 1.3.0 and later · before 1.3.0.130affected
- 1.4.0 and later · before 1.4.0.133affected
- 1.5.0 and later · before 1.5.0.135affected
- 2.0.0 and later · before 2.0.0.341affected
WSO2 WSO2 Open Banking IAM
- 2.0.0 and later · before 2.0.0.362affected
WSO2 WSO2 Open banking KM
- before 1.3.0unknown
- 1.3.0 and later · before 1.3.0.113affected
- 1.4.0 and later · before 1.4.0.129affected
- 1.5.0 and later · before 1.5.0.119affected
Affected versions · NVD (20)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- wso2 api manager2.2.0
- wso2 api manager2.5.0
- wso2 api manager2.6.0
- wso2 api manager3.0.0
- wso2 api manager3.1.0
- wso2 api manager3.2.0
- wso2 api manager3.2.1
- wso2 api manager4.0.0
- wso2 api manager4.1.0
- wso2 api manager4.2.0
- wso2 api manager4.3.0
- wso2 identity server5.10.0
- wso2 identity server5.11.0
- wso2 identity server5.3.0
- wso2 identity server5.4.0
- wso2 identity server5.4.1
- wso2 identity server5.5.0
- wso2 identity server5.6.0
- wso2 identity server5.7.0
- wso2 identity server5.8.0
Same product
wso2: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-29464Certain WSO2 products allow unrestricted file upload with resultant remote code execution.KEV99Now
- CVE-2020-24589The Management Console in WSO2 API Manager through 3.1.0 and API Microgateway 2.2.0 allows XML External Entity injection (XXE) attacks.44Plan
- CVE-2026-2053Unauthenticated Server-Side Request Forgery via WS-Addressing in WSO2 API Manager40Plan
Published before and after this one in the same product
- ← EarlierCVE-2024-5848Feb 27, 2025 · Reflected Cross-Site Scripting (XSS) in Multiple WSO2 Products Due to Improper Input Validation24Monitor
- ← EarlierCVE-2025-2905May 5, 2025 · An XML External Entity (XXE) vulnerability in Multiple WSO2 Products36Monitor
- Later →CVE-2024-5962May 22, 2025 · Reflected Cross-Site Scripting (XSS) in Authentication Endpoint of Multiple WSO2 Products Due to Missing Output Encoding24Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2023-6837524 days apartIncorrect Authorization in Multiple WSO2 Products via Federated Authentication with JIT Provisioning Leading to User Impersonation32Monitor
- CVE-2024-232184 days apartIncorrect Authorization in Multiple WSO2 Products Allows API Access via Refresh Token22Monitor
- CVE-2024-70968 days apartPrivilege Escalation in Multiple WSO2 Products via SOAP Admin Service Due to Business Logic Flaw21Monitor
- CVE-2024-70978 days apartIncorrect Authorization in Multiple WSO2 Products via SOAP Admin Service Allowing Unauthorized User Signup17Monitor
- CVE-2024-351132 days apartIncorrect Authorization in Multiple WSO2 Products Allows Unauthorized Access to Registry Versioned Files17Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-863 · Incorrect AuthorizationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.