dbcve.org
Identity ServerApplication · Wso2

CVE-2025-0663

MEDIUM · 6.8 CVSS v3.1 Published 2025-09-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
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
A cross-tenant authentication vulnerability exists in multiple WSO2 products due to improper cryptographic design in Adaptive Authentication. A single cryptographic key is used across all tenants to sign authentication cookies, allowing a privileged user in one tenant to forge authentication cookies for users in other tenants. Because the Auto-Login feature is enabled by default, this flaw may allow an attacker to gain unauthorized access and potentially take over accounts in other tenants. Successful exploitation requires access to Adaptive Authentication functionality, which is typically restricted to high-privileged users. The vulnerability is only exploitable when Auto-Login is enabled, reducing its practical impact in deployments where the feature is disabled.

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 · moderate confidence

A cross-tenant cryptographic flaw in WSO2's Adaptive Authentication uses a single shared key across all tenants to sign authentication cookies, enabling a privileged attacker in one tenant to forge cookies and impersonate users in other tenants. The vulnerability is exploitable only when Auto-Login is enabled, which is the default setting.

MitigationDisable the Auto-Login feature in Adaptive Authentication configurations immediately. For long-term remediation, implement tenant-specific cryptographic keys for cookie signing and rotate existing keys.

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:= 5.10.0= 5.11.0= 6.0.0= 6.1.0= 7.0.0
Identity Server As Key ManagerApplication
Affected:= 5.10.0
Open Banking IamApplication
Affected:= 2.0.0

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
Adjacent
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/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 product version
    Locate the version file in the installation directory. Check for a VERSION or product-version.txt file in the repository/components/ directory, or inspect the deployment.toml configuration file for the 'server' or 'productVersion' setting.
    Affected if The installed version matches 5.10.0, 5.11.0, 6.0.0, 6.1.0, or 7.0.0 for WSO2 Identity Server; 5.10.0 for Identity Server As Key Manager; or 2.0.0 for Open Banking Iam.
  2. Determine if Auto-Login is enabled in Adaptive Authentication
    Examine the authentication configuration. Check the deployment.toml file for 'Authentication.EnableAutoLogin' or 'AdaptiveAuthentication.AutoLogin' settings, or log into the management console and navigate to Login Preferences > Adaptive Authentication to verify the Auto-Login toggle status.
    Affected if The Auto-Login feature is set to true or enabled in the configuration.
  3. Verify the tenant configuration and cookie signing key
    Inspect the authentication.xml or authentication-config.xml file in the repository/conf/identity/ directory. Look for the 'SessionID' or 'Cookie' signing configuration to confirm if a tenant-specific or shared key is in use.
    Affected if The same signing key is used across multiple tenants, or no tenant-specific key segregation is configured.
  4. Check for cross-tenant access privileges
    Review user role assignments and tenant memberships in the management console under Users and Roles > List. Identify if the current environment has multiple active tenants with privileged users.
    Affected if Multiple tenants exist in the environment with users who have elevated privileges.

The environment is affected if running an affected version (5.10.0, 5.11.0, 6.0.0, 6.1.0, or 7.0.0) with Auto-Login enabled and multiple tenants configured.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable the Auto-Login feature in Adaptive Authentication configurations immediately. For long-term remediation, implement tenant-specific cryptographic keys for cookie signing and rotate existing keys.

Recommended fix Moderate confidence

Upgrade to the fixed version specified in the WSO2 security advisory for this CVE (check security.docs.wso2.com for product-specific fixed releases)

  1. 1. Identify the specific WSO2 product and version currently deployed from the affected list (Identity Server 5.10.0/5.11.0/6.0.0/6.1.0, Identity Server As Key Manager 5.10.0, or Open Banking Iam 2.0.0)
  2. 2. Navigate to the official WSO2 security advisory page at security.docs.wso2.com to obtain the specific fixed version for your product
  3. 3. Plan and schedule an upgrade to the fixed version recommended in the WSO2 security advisory
  4. 4. Before upgrading in production, test the upgrade in a staging environment to verify compatibility with existing configurations
  5. 5. After upgrading, verify that the Adaptive Authentication functionality works correctly with the new cryptographic implementation
  6. 6. Alternatively, if immediate upgrade is not feasible, confirm that Auto-Login is disabled in the authentication configuration to reduce exploitability (note: this is a mitigation, not a complete fix)
Caveat Review WSO2 release notes for the target version to check for breaking changes, especially regarding Adaptive Authentication behavior and tenant-specific key configurations

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 help mitigating

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-0663 — 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-0663 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