Skip to main content
Vulnerability Database/CVE-2025-10149

CVE-2025-10149: SCIM Endpoint Authorization Bypass Vulnerability

CVE-2025-10149 is an authorization bypass flaw in SCIM endpoints affecting federated user authentication. Attackers can exploit username collisions to perform unauthorized operations on local accounts. This article covers technical details, impact analysis, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2025-10149 Overview

CVE-2025-10149 is an authorization flaw in the System for Cross-domain Identity Management (SCIM) endpoint implemented in WSO2 products. The endpoint fails to adequately validate authorization for federated users when operations target the local user store. When a local user and a federated user share the same username, the federated user can execute operations against the matching local account. An attacker authenticated as a federated user can invoke SCIM 2.0 or SCIM 1.1 endpoints to perform arbitrary operations on local user accounts, leading to account takeover. Deployments that disable user self-registration are rated at reduced severity by the vendor.

Critical Impact

A federated user can take over local user accounts sharing the same username through SCIM 1.1 or SCIM 2.0 operations, with no user interaction required.

Affected Products

  • WSO2 products exposing SCIM 2.0 endpoints with federated authentication enabled
  • WSO2 products exposing SCIM 1.1 endpoints with federated authentication enabled
  • Deployments allowing user self-registration (full severity scope)

Discovery Timeline

  • 2026-10-19 - CVE-2025-10149 published to the National Vulnerability Database (NVD)
  • 2026-10-20 - Record last modified in NVD

Technical Details for CVE-2025-10149

Vulnerability Analysis

The flaw is categorized under [CWE-281: Improper Preservation of Permissions]. The SCIM endpoint resolves target users by username without enforcing a strict boundary between the local user store and federated identity sources. When a federated user authenticates and issues a SCIM request, the handler locates a username match in the local store and applies the operation to that local account. The federated principal inherits the ability to modify or control the local identity, including attributes such as password, email, and group membership.

Successful exploitation grants an attacker administrative control over the targeted local account. Deployments that permit self-registration expand the attack surface, because adversaries can register a federated identity with any desired username and immediately pivot to the matching local user. This elevates the issue from an insider-adjacent abuse case to a remotely exploitable account takeover primitive.

Root Cause

The SCIM request handler does not segregate operations by identity source. Authorization checks confirm that the caller is authenticated and holds SCIM operation privileges, but they do not verify that the caller owns, or is authorized to manage, the target local account. The username collision between the federated and local realms is treated as implicit authorization.

Attack Vector

Exploitation requires network access to the SCIM endpoints and a valid federated session. The attacker crafts standard SCIM user operations referencing the shared username. The server routes the operation to the local user store and executes it under the federated session's authority. See the WSO2 Security Advisory WSO2-2025-4438 for product-specific exploit conditions.

// No verified exploit code published. The vendor advisory describes the
// abuse pattern: an authenticated federated user issues SCIM 2.0 or
// SCIM 1.1 PATCH/PUT operations against /scim2/Users/{id} or the
// SCIM 1.1 equivalent, where {id} resolves to a local user that shares
// the federated user's username.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2025-10149

Indicators of Compromise

  • SCIM 2.0 or SCIM 1.1 requests originating from sessions tied to federated identity providers but modifying local user records.
  • Unexpected password resets, email changes, or group membership updates on local accounts that mirror federated usernames.
  • Creation of federated identities whose usernames collide with privileged local accounts such as admin.

Detection Strategies

  • Correlate SCIM audit logs with authentication logs to identify operations where the acting principal is federated but the target user resides in the local store.
  • Alert on SCIM PATCH or PUT operations against privileged local accounts outside approved administrative workflows.
  • Baseline SCIM endpoint usage per identity source and flag deviations in request volume or operation type.

Monitoring Recommendations

  • Enable verbose SCIM request logging on /scim2/Users and /wso2/scim/Users endpoints, including the authenticated subject and identity provider.
  • Forward WSO2 Identity Server logs to a centralized analytics platform for cross-source correlation.
  • Monitor self-registration events for usernames matching existing local accounts and treat them as high-priority alerts.

How to Mitigate CVE-2025-10149

Immediate Actions Required

  • Apply the WSO2-provided patch or upgrade referenced in WSO2 Security Advisory WSO2-2025-4438.
  • Audit the local user store for usernames that overlap with federated identities and remediate collisions.
  • Disable user self-registration until patches are deployed if the deployment supports federated login.

Patch Information

WSO2 has published remediation guidance in advisory WSO2-2025-4438. Administrators should consult the advisory for the exact product versions, patch bundles, and configuration changes required. No public exploit has been reported, and the vulnerability is not listed on the CISA Known Exploited Vulnerabilities catalog as of the advisory date.

Workarounds

  • Restrict SCIM 1.1 and SCIM 2.0 endpoint access to trusted administrative networks using reverse-proxy or WAF rules.
  • Enforce distinct username namespaces between federated identity providers and the local user store.
  • Revoke SCIM operation scopes from federated users where business workflows do not require them.
bash
# Example: restrict SCIM endpoints at the reverse proxy layer
location /scim2/ {
    allow 10.0.0.0/24;    # administrative subnet
    deny all;
    proxy_pass https://wso2-identity-server:9443;
}

location /wso2/scim/ {
    allow 10.0.0.0/24;
    deny all;
    proxy_pass https://wso2-identity-server:9443;
}

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.