dbcve.org
Identity ServerApplication · Wso2

CVE-2025-9973

HIGH · 7.2 CVSS v3.1 Published 2026-05-11
Fix available
A fix is available. Upgrade to 7.1.0.26 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Due to not validating the organization context when executing adaptive authentication flows, the WSO2 Identity Server allows adaptive authentication logic to be triggered on unintended organizations. A malicious actor with privileges to configure adaptive authentication within one organization can leverage this functionality to execute authentication logic on other organizations and sub-organizations. This flaw allows bypassing authorization boundaries between organizations, leading to unauthorized access to critical operations and user accounts in other organizations. When adaptive authentication is enabled in a multi-organization deployment, a malicious actor with privileges to configure adaptive authentication in one organization could exploit this feature to perform critical operations in other organizations without authorization. This may result in privilege escalation, unauthorized access to resources, and potential account takeover across organizations.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

WSO2 Identity Server fails to validate organization context during adaptive authentication flow execution. An authenticated user with privileges to configure adaptive authentication in one organization can trigger authentication logic in other organizations or sub-organizations, bypassing authorization boundaries between tenants.

MitigationImplement proper organization context validation in adaptive authentication workflows to ensure authentication logic only executes within the authorized organization scope.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Identity ServerApplication
Affected:>= 7.1.0, < 7.1.0.26

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed WSO2 Identity Server version
    Check the product version via the admin console (Server -> Manage -> Version) or by examining the product-info.xml file in the installation directory, or run: java -jar carbon-version*.jar
    Affected if The installed version is 7.1.0 or higher but lower than 7.1.0.26
  2. Confirm adaptive authentication is enabled
    Log in to the WSO2 Identity Server admin console and navigate to Identity Providers -> Resident -> Adaptive Authentication, or inspect the application-authentication.xml configuration file in the <IS_HOME>/repository/conf/identity/ directory for enabled authentication scripts
    Affected if Adaptive authentication scripts or templates are configured for any application in the environment
  3. Verify multi-organization or tenant configuration exists
    Access the WSO2 admin console and check for multiple organizations under the Organization Management section, or inspect the tenant-conf.json file in the repository/conf directory to identify configured super tenants or multiple organizations
    Affected if More than one organization or tenant is configured beyond the primary organization
  4. Review adaptive authentication scripts for organization context handling
    Examine the authentication scripts configured in application-authentication.xml or via the Management Console under Service Providers -> Script Based Adaptive Authentication. Look for the use of 'organization' or 'context' variables that may not include proper organization boundary validation
    Affected if Adaptive authentication scripts exist that reference organization context without explicit organization-scoped validation checks

The environment is affected if WSO2 Identity Server version is 7.1.0 through 7.1.0.25 AND adaptive authentication is configured in an environment with multiple organizations or tenants.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.1.0.26 or later
Fixed in 7.1.0.26
Interim mitigation

Implement proper organization context validation in adaptive authentication workflows to ensure authentication logic only executes within the authorized organization scope.

Recommended fix High confidence

7.1.0.26 or later (within the 7.1.x branch)

  1. Upgrade WSO2 Identity Server to version 7.1.0.26 or later
  2. After upgrading, verify that adaptive authentication flows are functioning correctly in the organization context
  3. Review adaptive authentication configurations across all organizations to ensure proper organization boundaries are enforced
  4. Test that authentication flows in sub-organizations cannot be manipulated by users from other organizations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Identity Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-9973 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-9973 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data