CVE-2025-5605
Authentication Bypass via URI Manipulation in Multiple WSO2 Products' Management Console Leading to Partial Information Disclosure
MEDIUM
5.3
CVSS Score
Published: October 24, 2025 at 10:09 AM UTC
Updated: June 17, 2026 at 09:48 AM UTC
10 products affected across 1 vendorAPI ManagerIdentity ServerIdentity Server As Key Manager
Using WSO2 Identity Server by WSO2?
Get instant alerts when new vulnerabilities affect WSO2 Identity Server - before attackers find them.
Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.3
Exploit prediction
EPSS 0.9%
SSVC
No known exploit
Description
An authentication bypass vulnerability exists in the Management Console of multiple WSO2 products. A malicious actor with access to the console can manipulate the request URI to bypass authentication and access certain restricted resources, resulting in partial information disclosure. The known exposure from this issue is limited to memory statistics. While the vulnerability does not allow full account compromise, it still enables unauthorized access to internal system details.
Affected
Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.
4.5.0 ≤ v < 4.5.0.114.5.0
Affected range stops below 4.5.0.11, so it looks safe — our inference, not a vendor statement
3.1.0 ≤ v < 3.1.0.3343.2.0 ≤ v < 3.2.0.4303.2.1 ≤ v < 3.2.1.484.0.0 ≤ v < 4.0.0.3464.1.0 ≤ v < 4.1.0.2104.2.0 ≤ v < 4.2.0.1484.3.0 ≤ v < 4.3.0.614.4.0 ≤ v < 4.4.0.244.5.0 ≤ v < 4.5.0.103.1.03.2.03.2.14.0.04.1.04.2.04.3.04.4.04.5.0
Affected range stops below 3.1.0.334, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.2.0.430, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.2.1.48, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.0.0.346, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.1.0.210, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.2.0.148, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.3.0.61, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.4.0.24, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.5.0.10, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 3.1.0 (unknown)
6.6.0 ≤ v < 6.6.0.2176.6.0
Affected range stops below 6.6.0.217, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.6.0 (unknown)
5.10.0 ≤ v < 5.10.0.3615.11.0 ≤ v < 5.11.0.4146.0.0 ≤ v < 6.0.0.2456.1.0 ≤ v < 6.1.0.2447.0.0 ≤ v < 7.0.0.1197.1.0 ≤ v < 7.1.0.255.10.05.11.06.0.06.1.07.0.07.1.0
Affected range stops below 5.10.0.361, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.11.0.414, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.0.0.245, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.1.0.244, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.0.0.119, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.1.0.25, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.10.0 (unknown)
5.10.0 ≤ v < 5.10.0.3545.10.0
Affected range stops below 5.10.0.354, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.10.0 (unknown)
2.0.0 ≤ v < 2.0.0.3822.0.0
Affected range stops below 2.0.0.382, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 2.0.0 (unknown)
2.0.0 ≤ v < 2.0.0.4032.0.0
Affected range stops below 2.0.0.403, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 2.0.0 (unknown)
4.5.0 ≤ v < 4.5.0.104.5.0
Affected range stops below 4.5.0.10, so it looks safe — our inference, not a vendor statement
4.5.0 ≤ v < 4.5.0.104.5.0
Affected range stops below 4.5.0.10, so it looks safe — our inference, not a vendor statement
4.10.42 ≤ v < 4.10.42.104.10.9 ≤ v < 4.10.9.684.5.3 ≤ v < 4.5.3.404.6.0 ≤ v < 4.6.0.12244.6.1 ≤ v < 4.6.1.1504.6.2 ≤ v < 4.6.2.6644.6.3 ≤ v < 4.6.3.324.6.4 ≤ v < 4.6.4.84.7.1 ≤ v < 4.7.1.694.8.1 ≤ v < 4.8.1.334.9.0 ≤ v < 4.9.0.1004.9.26 ≤ v < 4.9.26.204.9.27 ≤ v < 4.9.27.44.9.28 ≤ v < 4.9.28.44.10.424.10.94.5.34.6.04.6.14.6.24.6.34.6.44.7.14.8.14.9.04.9.264.9.274.9.28
Affected range stops below 4.10.42.10, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.10.9.68, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 4.10.90 (unaffected)
Affected range stops below 4.5.3.40, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.6.0.1224, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.6.1.150, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.6.2.664, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.6.3.32, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.6.4.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.7.1.69, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.8.1.33, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.9.0.100, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.9.26.20, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.9.27.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.9.28.4, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 4.9.29 (unaffected)
Remediation
No guide yetNo remediation guidance has been written for this CVE yet. What the record does show:
Patch and advisory references
References (1)
Vendor Advisory
Source: ed10eef1-636d-4fbe-9993-6890dfa878f8
https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2025/WSO2-2025-4115/SSVC — Action Prioritization
SSVCNo known exploitNot automatablePartial impact
SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.
CVSS
- Attack Vector
- NETWORK
- Complexity
- LOW
- Privileges
- NONE
- User Interaction
- NONE
- Scope
- UNCHANGED
- Confidentiality
- LOW
- Integrity
- NONE
- Availability
- NONE
Vector?
Quick Info
StatusANALYZED
CWE
CWE-290
Get alerted
Stop reading CVE feeds looking for your own stack
Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.
Free plan, no card