# CVE-2025-0663: Auth bypass in WSO2 Identity Server

> Privileged users can forge authentication cookies to take over accounts in other tenants due to shared cryptographic keys in WSO2 Identity Server.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2025
- **Updated:** 25 Sep 2025
- **Also known as:** GHSA-9c82-vpf4-hvh3

## What is CVE-2025-0663?

CVE-2025-0663 is a medium-severity authentication bypass vulnerability in Wso2 Identity Server, published on 23 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2025-0663?

It affects 3 products.


Products: Wso2 Identity Server, Wso2 Identity Server as Key Manager, Wso2 Open Banking Iam.

## How do I fix CVE-2025-0663?

No fix has been published for CVE-2025-0663 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-0663 being exploited?

There is no known exploitation of CVE-2025-0663 in the wild and no public exploit code.

## Other vulnerabilities in Wso2 Identity Server

- [CVE-2016-4311](https://insights.sbomify.com/CVE-2016-4311/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2025-10470](https://insights.sbomify.com/CVE-2025-10470/): Denial-of-Service via Magic Link Authentication in WSO2 Identity Server Allows Service Unavailability (high 8.6)
- [CVE-2025-12107](https://insights.sbomify.com/CVE-2025-12107/): Server-Side Template Injection via Velocity Template Engine in Multiple WSO2 Products Allows Remote Code Execution (high 8.4)
- [CVE-2016-4312](https://insights.sbomify.com/CVE-2016-4312/): XML external entity in n/a (high 7.5)
- [CVE-2025-10908](https://insights.sbomify.com/CVE-2025-10908/): Account Lock Bypass via Magic Link or Pass Key Authentication in WSO2 Identity Server Allows Unauthorized Access (high 7.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-0663 and fix it if it is affected.

What it is: CVE-2025-0663 is a medium-severity authentication bypass vulnerability in Wso2 Identity Server, published on 23 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-0663 in the wild and no public exploit code.

Affected product: Wso2 Identity Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-0663/ (Markdown: https://insights.sbomify.com/CVE-2025-0663/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-0663
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-0663
- OSV: https://osv.dev/vulnerability/CVE-2025-0663

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-0663/
Summaries are generated and may contain mistakes; the official description above is the record.