CVE-2025-0663: Vulnerability in WSO2 WSO2 Open Banking IAM
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.
AI Analysis
Technical Summary
CVE-2025-0663 is a cross-tenant authentication vulnerability identified in WSO2 Open Banking IAM version 2.0.0. The root cause lies in the improper cryptographic design of the Adaptive Authentication feature, where a single cryptographic key is used across all tenants to sign authentication cookies. This design flaw enables a privileged user within one tenant to forge authentication cookies for users in other tenants, effectively bypassing tenant isolation. The vulnerability is exacerbated by the Auto-Login feature, which is enabled by default. This feature automatically logs in users based on authentication cookies, so if an attacker can forge these cookies, they may gain unauthorized access to accounts in other tenants without additional user interaction. Exploitation requires access to Adaptive Authentication functionality, which is typically restricted to high-privileged users, limiting the attack surface. The vulnerability does not require user interaction but does require a privileged user context within a tenant. The CVSS 3.1 score is 6.8 (medium severity), reflecting the attack vector as adjacent network, low attack complexity, high privileges required, no user interaction, and high impact on confidentiality, integrity, and availability. There are no known exploits in the wild, and no patches have been published yet. The vulnerability corresponds to CWE-287 (Improper Authentication).
Potential Impact
For European organizations using WSO2 Open Banking IAM 2.0.0, this vulnerability poses a significant risk to multi-tenant environments, particularly in financial institutions and service providers managing multiple client tenants. Unauthorized cross-tenant access could lead to data breaches, financial fraud, and regulatory non-compliance, especially under GDPR and PSD2 frameworks. The compromise of authentication cookies could allow attackers to impersonate users across tenants, potentially leading to account takeover, unauthorized transactions, and exposure of sensitive personal and financial data. The impact extends to loss of trust, legal penalties, and operational disruption. Since exploitation requires high privileges, insider threats or compromised administrative accounts are the primary risk vectors. The default enabled Auto-Login feature increases risk in typical deployments. Organizations with strict tenant isolation requirements and those operating in regulated sectors are particularly vulnerable.
Mitigation Recommendations
To mitigate this vulnerability, European organizations should immediately review and disable the Auto-Login feature in WSO2 Open Banking IAM deployments where it is not essential, reducing the risk of cookie forgery exploitation. Restrict access to Adaptive Authentication functionality to the minimum necessary set of highly trusted administrators and implement strict role-based access controls (RBAC) and monitoring of privileged user activities. Employ network segmentation and multi-factor authentication (MFA) for administrative access to reduce the risk of privilege escalation. Monitor authentication logs for anomalies indicative of cross-tenant cookie forgery attempts. Organizations should engage with WSO2 for updates and patches addressing this cryptographic design flaw and plan for prompt patch deployment once available. Additionally, consider implementing tenant-specific cryptographic keys for signing authentication cookies as a long-term architectural improvement to prevent cross-tenant attacks. Conduct regular security audits and penetration testing focused on multi-tenant isolation controls.
Affected Countries
United Kingdom, Germany, France, Netherlands, Sweden, Spain, Italy
CVE-2025-0663: Vulnerability in WSO2 WSO2 Open Banking IAM
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.
AI-Powered Analysis
Technical Analysis
CVE-2025-0663 is a cross-tenant authentication vulnerability identified in WSO2 Open Banking IAM version 2.0.0. The root cause lies in the improper cryptographic design of the Adaptive Authentication feature, where a single cryptographic key is used across all tenants to sign authentication cookies. This design flaw enables a privileged user within one tenant to forge authentication cookies for users in other tenants, effectively bypassing tenant isolation. The vulnerability is exacerbated by the Auto-Login feature, which is enabled by default. This feature automatically logs in users based on authentication cookies, so if an attacker can forge these cookies, they may gain unauthorized access to accounts in other tenants without additional user interaction. Exploitation requires access to Adaptive Authentication functionality, which is typically restricted to high-privileged users, limiting the attack surface. The vulnerability does not require user interaction but does require a privileged user context within a tenant. The CVSS 3.1 score is 6.8 (medium severity), reflecting the attack vector as adjacent network, low attack complexity, high privileges required, no user interaction, and high impact on confidentiality, integrity, and availability. There are no known exploits in the wild, and no patches have been published yet. The vulnerability corresponds to CWE-287 (Improper Authentication).
Potential Impact
For European organizations using WSO2 Open Banking IAM 2.0.0, this vulnerability poses a significant risk to multi-tenant environments, particularly in financial institutions and service providers managing multiple client tenants. Unauthorized cross-tenant access could lead to data breaches, financial fraud, and regulatory non-compliance, especially under GDPR and PSD2 frameworks. The compromise of authentication cookies could allow attackers to impersonate users across tenants, potentially leading to account takeover, unauthorized transactions, and exposure of sensitive personal and financial data. The impact extends to loss of trust, legal penalties, and operational disruption. Since exploitation requires high privileges, insider threats or compromised administrative accounts are the primary risk vectors. The default enabled Auto-Login feature increases risk in typical deployments. Organizations with strict tenant isolation requirements and those operating in regulated sectors are particularly vulnerable.
Mitigation Recommendations
To mitigate this vulnerability, European organizations should immediately review and disable the Auto-Login feature in WSO2 Open Banking IAM deployments where it is not essential, reducing the risk of cookie forgery exploitation. Restrict access to Adaptive Authentication functionality to the minimum necessary set of highly trusted administrators and implement strict role-based access controls (RBAC) and monitoring of privileged user activities. Employ network segmentation and multi-factor authentication (MFA) for administrative access to reduce the risk of privilege escalation. Monitor authentication logs for anomalies indicative of cross-tenant cookie forgery attempts. Organizations should engage with WSO2 for updates and patches addressing this cryptographic design flaw and plan for prompt patch deployment once available. Additionally, consider implementing tenant-specific cryptographic keys for signing authentication cookies as a long-term architectural improvement to prevent cross-tenant attacks. Conduct regular security audits and penetration testing focused on multi-tenant isolation controls.
Affected Countries
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- WSO2
- Date Reserved
- 2025-01-23T06:40:05.025Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 68d2d2a01f3dbb78c7815c79
Added to database: 9/23/2025, 5:02:24 PM
Last enriched: 10/1/2025, 12:37:47 AM
Last updated: 1/7/2026, 6:10:13 AM
Views: 120
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-14835: CWE-80 Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) in opajaap WP Photo Album Plus
HighCVE-2026-0650: CWE-306 Missing Authentication for Critical Function in OpenFlagr Flagr
CriticalCVE-2025-15474: CWE-770 Allocation of Resources Without Limits or Throttling in AuntyFey AuntyFey Smart Combination Lock
MediumCVE-2025-14468: CWE-352 Cross-Site Request Forgery (CSRF) in mohammed_kaludi AMP for WP – Accelerated Mobile Pages
MediumCVE-2025-9611: CWE-749 Exposed Dangerous Method or Function in Microsoft Playwright
HighActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.