CVE-2025-10149 json
Arbitrary Operations via SCIM Endpoints in Multiple WSO2 Products Enables User Account Takeover
published 2026-10-19 20 d ago modified 2026-11-04 4 d ago also EUVD-2025-211118
- cvss
- 8.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 7%
- public exploits
- 0
- none known
Summary
The SCIM endpoint does not sufficiently validate authorization for federated users when performing operations against the local user store. This occurs when a local and a federated user share the same username, allowing a federated user to perform actions intended for a local user, including arbitrary operations.
A malicious actor authenticated as a federated user may perform arbitrary operations on local user accounts via the SCIM 2.0 or SCIM 1.1 endpoints when local and federated users share the same username. This could lead to user account takeover. Deployments that do not support user self-registration are considered medium severity.
Patch / fix
- WSO2 WSO2 Identity Server as Key Manager 5.10.0.370
- WSO2 WSO2 Open Banking IAM 2.0.0.419
- WSO2 WSO2 Identity Server 5.10.0.379, 5.11.0.415, 6.0.0.251, 6.1.0.251, 7.0.0.127, 7.1.0.34
- WSO2 WSO2 Carbon SCIM Common Component 5.6.0.1, 5.6.1.2, 5.7.0.3, 5.7.1.1, 5.7.7.1, 5.7.8.1
- WSO2 WSO2 Carbon SCIM 2.0 Common Component 1.5.1.40, 1.5.46.47
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 19 d ago
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N |
Affected products
- WSO2 WSO2 Identity Server as Key Manager
- WSO2 WSO2 Open Banking IAM
- WSO2 WSO2 Identity Server
- WSO2 WSO2 Carbon SCIM Common Component
- WSO2 WSO2 Carbon SCIM 2.0 Common Component
Classification
References
Sources
- CVE List CVE-2025-10149
- NVD CVE-2025-10149
Fencer Vulns 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.