CVE-2025-11850

Improper Implicit Association via User Store Initialization in WSO2 Identity Server [Identity Confusion / External IDP Use]

Published Aug 6, 2026 CVSS 3.1 · 4.3 Medium EPSS < 1% KEV · Not listed
Description
When secondary user stores are configured, the implicit-association resolver incorrectly initializes from a secondary user store and bypasses the primary user store during search and uniqueness checks. This allows a subject to be associated with an unintended local account if the same lookup claim (e.g., username or email) exists in both the primary and a secondary store.

If duplicate claim values exist across user stores, this issue can lead to identity confusion due to incorrect implicit associations when using an external Identity Provider (IDP). Legitimate user accounts in the primary user store may fail to associate correctly with their corresponding external IDP accounts, potentially restricting access if the secondary account has fewer privileges. Deployments are not affected if no secondary user stores are configured, implicit association is disabled, or claim values are globally unique.

Analysis

AI-generated

Technical impact

A flaw in the implicit‑association resolver incorrectly initializes from a secondary user store and skips checks against the primary store during lookup and uniqueness validation. This can incorrectly bind a subject to an unintended local account when the same lookup claim, such as a username or e‑mail address, exists in both stores. The resulting identity confusion may allow an attacker to gain access to an account with fewer privileges or hamper legitimate users from linking their external Identity Provider account, potentially leading to unauthorized access or denied service.

Affected Systems

The vulnerability affects WSO2 Token Exchange Grant Type for OAuth and WSO2 Identity Server when a secondary user store is configured. Version information was not specified in the CNA data, meaning any installation that uses secondary stores is potentially impacted. Deployments that do not configure secondary stores, disable implicit association, or enforce globally unique claim values are not affected.

Risk and Exploitability

With a CVSS score of 4.3 the vulnerability rates as low‑to‑medium severity, and the EPSS score is 0.00219, indicating a very low likelihood of exploitation. It is also not listed in the CISA KEV catalog. Exploitation requires an environment configured with secondary user stores and an external Identity Provider that supplies duplicate claim values. The attack vector is therefore an indirect configuration‑based weakness rather than an active exploitation surface; however, the impact on account integrity warrants prompt remediation.

Remediation

Vendor Solution

Follow the instructions given on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4493/#solution


OpenCVE Recommended Actions

  • Apply the official patch or upgrade package provided by WSO2 as described in the 2025‑4493 advisory
  • If immediate patching is not possible, disable implicit user‑store association or enforce unique claim values across all stores
  • Remove or avoid configuring secondary user stores unless essential for your deployment environment

Generated by OpenCVE AI on August 6, 2026 at 15:07 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Wso2 identity Server
Vendors & Products Wso2 identity Server
Type Values Removed Values Added
Weaknesses CWE-639
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-287
Type Values Removed Values Added
Description When secondary user stores are configured, the implicit-association resolver incorrectly initializes from a secondary user store and bypasses the primary user store during search and uniqueness checks. This allows a subject to be associated with an unintended local account if the same lookup claim (e.g., username or email) exists in both the primary and a secondary store. If duplicate claim values exist across user stores, this issue can lead to identity confusion due to incorrect implicit associations when using an external Identity Provider (IDP). Legitimate user accounts in the primary user store may fail to associate correctly with their corresponding external IDP accounts, potentially restricting access if the secondary account has fewer privileges. Deployments are not affected if no secondary user stores are configured, implicit association is disabled, or claim values are globally unique.
Title Improper Implicit Association via User Store Initialization in WSO2 Identity Server [Identity Confusion / External IDP Use]
First Time appeared Wso2
Wso2 token Exchange Grant Type For Oauth
Wso2 wso2 Identity Server
CPEs cpe:2.3:a:wso2:token_exchange_grant_type_for_oauth:*:*:*:*:*:*:*:*
cpe:2.3:a:wso2:wso2_identity_server:*:*:*:*:*:*:*:*
Vendors & Products Wso2
Wso2 token Exchange Grant Type For Oauth
Wso2 wso2 Identity Server
References
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L'}

Weaknesses
  • CWE-287

    Improper Authentication

  • CWE-639

    Authorization Bypass Through User-Controlled Key

Sources

Status
PUBLISHED
Assigner
WSO2
Published
Updated
Aug 6, 2026, 12:36 PM
Reserved
Oct 16, 2025, 10:51 AM
Status
Analyzed
Published
Aug 6, 2026, 8:16 AM
Modified
Sep 29, 2026, 2:10 PM