CVE-2025-10149 — Arbitrary Operations via SCIM Endpoints in Multiple WSO2 Products Enables User Account Takeover
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (WSO2 Identity Server, WSO2 Identity Server As Key Manager, WSO2 Open Banking Iam…).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| WSO2 | Identity Server | ≥ 5.10.0 and < 5.10.0.379≥ 5.11.0 and < 5.11.0.415≥ 6.0.0 and < 6.0.0.251≥ 6.1.0 and < 6.1.0.251≥ 7.0.0 and < 7.0.0.127≥ 7.1.0 and < 7.1.0.34 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| WSO2 | Identity Server As Key Manager | ≥ 5.10.0 and < 5.10.0.370 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| WSO2 | Open Banking Iam | ≥ 2.0.0 and < 2.0.0.419 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| WSO2 | WSO2 Carbon SCIM 2.0 Common Component | ≥ 1.5.1 and < 1.5.1.40≥ 1.5.46 and < 1.5.46.47 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| WSO2 | WSO2 Carbon SCIM Common Component | ≥ 5.6.0 and < 5.6.0.1≥ 5.6.1 and < 5.6.1.2≥ 5.7.0 and < 5.7.0.3≥ 5.7.1 and < 5.7.1.1≥ 5.7.7 and < 5.7.7.1≥ 5.7.8 and < 5.7.8.1 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 8.2 | CVSS 3.1 | High | 3.9 | 4.2 | ed10eef1-636d-4fbe-9993-6890dfa878f8 via NIST National Vulnerability Database |
| 8.2 | CVSS 3.1 | High | — | — | WSO2 via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N (score shown at the top: ed10eef1-636d-4fbe-9993-6890dfa878f8) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Timeline
What happened to this CVE, newest first.
- 2026
- Source status changed · Received → Awaiting Analysis
- Affected products added · wso2/wso2 identity server as key manager, wso2/wso2 open banking iam, wso2/wso2 identity server, wso2/wso2 carbon scim c
- Record published
- CVSS changed · 8.2
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 19, 2026 – Oct 19, 2026
- 1× Official description updated · Oct 19, 2026 – Oct 19, 2026
References
1 on the record
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2025-7203 Sensitive Information Disclosure via Management Console and Product Files in Multiple WSO2 Products Allows Retrieval of Credentials 6h
- Medium CVE-2025-13591 Username Enumeration via Authentication Endpoint in WSO2 Identity Server Allows User Account Discovery 6h
- Medium CVE-2025-13173 Improper Token Revocation via Session-Bound Token Flow in Multiple WSO2 Products Allows Unauthorized Access After Session Termination 6h
- Low CVE-2024-4412 Expression Language Injection via User Input in Multiple WSO2 Products Permits Arbitrary Operations 6h
- Unknown CVE-2024-4457 Remote Code Execution via JDBC User Store Configuration in Multiple WSO2 Products Allows Arbitrary Code Execution 1d
- Medium CVE-2024-8122 Potential brute force vulnerability due to non-expiring SMS OTPs 11d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No FIRST EPSS score.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-10149 is "Arbitrary Operations via SCIM Endpoints in Multiple WSO2 Products Enables User Account Takeover", rated High. It affects Identity Server (WSO2); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.2 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.