Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 0.85% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2025
CVE-2025-5605High confidence
Authentication Bypass via URI Manipulation in Multiple WSO2 Products' Management Console Leading to Partial Information Disclosure
WSO2 · WSO2 Identity Server
4.3MediumCVSS 3.1
Scheduled
Patch availableMedium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityMedium→Operational priority:Medium, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict local access and enforce least privilege on affected hosts.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs WSO2 WSO2 Identity Server and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
Patch available01
What, why and how
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.
What
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.
Why
This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.
How
An attacker operating through an adjacent network may attempt exploitation without authentication or user interaction. If successful, the issue may bypass an access boundary or take over an account.
What
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.
Why
This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.
How
An attacker operating through an adjacent network may attempt exploitation without authentication or user interaction. If successful, the issue may bypass an access boundary or take over an account.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- an adjacent network → Authentication Bypass by Spoofing → bypass an access boundary or take over an account
- Attack surface
- Adjacent
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-290 ↗
CWE-290: Authentication Bypass by Spoofing. This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVAdjacentAttack vector: The attacker must be on an adjacent or logically close network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CLowConfidentiality impact: A successful attack can cause a limited loss.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.- Post-exploitation / living off the land
- Stolen credentials, tokens and legitimate administration functions may provide continued access without deploying a large custom toolset.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Patch available
- Affected
- WSO2 Identity Server: < 5.10.0, 5.10.0 < 5.10.0.361, 5.11.0 < 5.11.0.414, 6.0.0 < 6.0.0.245, 6.1.0 < 6.1.0.244, 7.0.0 < 7.0.0.119, 7.1.0 < 7.1.0.25
- WSO2 Enterprise Integrator: < 6.6.0, 6.6.0 < 6.6.0.217
- WSO2 Universal Gateway: 4.5.0 < 4.5.0.10
- WSO2 Traffic Manager: 4.5.0 < 4.5.0.10
- WSO2 API Manager: < 3.1.0, 3.1.0 < 3.1.0.334, 3.2.0 < 3.2.0.430, 3.2.1 < 3.2.1.48, 4.0.0 < 4.0.0.346, 4.1.0 < 4.1.0.210, 4.2.0 < 4.2.0.148, 4.3.0 < 4.3.0.61, 4.4.0 < 4.4.0.24, 4.5.0 < 4.5.0.10
- WSO2 API Control Plane: 4.5.0 < 4.5.0.11
- WSO2 Identity Server as Key Manager: < 5.10.0, 5.10.0 < 5.10.0.354
- WSO2 Open Banking AM: < 2.0.0, 2.0.0 < 2.0.0.382
- WSO2 Open Banking IAM: < 2.0.0, 2.0.0 < 2.0.0.403
- org.wso2.carbon:org.wso2.carbon.ui: 4.5.3 < 4.5.3.40, 4.6.0 < 4.6.0.1224, 4.6.1 < 4.6.1.150, 4.6.2 < 4.6.2.664, 4.6.3 < 4.6.3.32, 4.6.4 < 4.6.4.8, 4.7.1 < 4.7.1.69, 4.8.1 < 4.8.1.33, 4.9.0 < 4.9.0.100, 4.9.26 < 4.9.26.20, 4.9.27 < 4.9.27.4, 4.9.28 < 4.9.28.4, 4.10.9 < 4.10.9.68, 4.10.42 < 4.10.42.10
- Action
- Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
- Workaround
- No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04
Evidence and provenance
Published 24 Oct 2025 · Last source change 24 Oct 2025, 11:44 UTC · CWE-290 · Authentication Bypass by Spoofing
CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2025-35828
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCISA ADP
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.