Medium

CVE-2025-13173 — Improper Token Revocation via Session-Bound Token Flow in Multiple WSO2 Products Allows Unauthorized Access After Session Termination

Tokens associated with user sessions are not revoked when the corresponding user session is terminated, unless another SSO request is initiated. This occurs when the session-bound token feature is enabled with token binding validation and the "Revoke token upon user logout" option is not active. The software fails to automatically invalidate session-bound tokens upon user session termination. This vulnerability exists when token binding validation is enabled. As a result, a malicious actor possessing a valid session-bound token could exploit this condition to maintain unauthorized access to applications and resources even after the associated user session has ended, potentially leading to the exposure of sensitive user data.

Published Oct 19, 2026 · Updated Oct 19, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: WSO2

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

—

No EPSS score.

Affects

WSO2

Api Control Plane and 8 more

CVSS base

6.5

Medium · 2 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (WSO2 Api Control Plane, WSO2 Api Manager, WSO2 Identity Server…).
The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
WSO2	Api Control Plane	≥ 4.6.0 and < 4.6.0.13≥ 4.5.0 and < 4.5.0.47	Vulnerable	CVE Program (cve.org) e CISA ADP
WSO2	Api Manager	≥ 4.3.0 and < 4.3.0.97≥ 4.6.0 and < 4.6.0.11≥ 4.5.0 and < 4.5.0.46≥ 4.4.0 and < 4.4.0.61≥ 4.2.0 and < 4.2.0.186≥ 4.1.0 and < 4.1.0.246≥ 4.0.0 and < 4.0.0.376≥ 3.2.1 and < 3.2.1.81 and 2 more ≥ 3.2.0 and < 3.2.0.456≥ 3.1.0 and < 3.1.0.352	Vulnerable	CVE Program (cve.org) e CISA ADP
WSO2	Identity Server	≥ 7.0.0 and < 7.0.0.133≥ 7.2.0 and < 7.2.0.3≥ 7.1.0 and < 7.1.0.41≥ 6.1.0 and < 6.1.0.256≥ 6.0.0 and < 6.0.0.255≥ 5.10.0 and < 5.10.0.381≥ 5.11.0 and < 5.11.0.428	Vulnerable	CVE Program (cve.org) e CISA ADP
WSO2	Identity Server As Key Manager	≥ 5.10.0 and < 5.10.0.372	Vulnerable	CVE Program (cve.org) e CISA ADP
WSO2	Open Banking Am	≥ 2.0.0 and < 2.0.0.401	Vulnerable	CVE Program (cve.org) e CISA ADP
WSO2	Open Banking Iam	≥ 2.0.0 and < 2.0.0.421	Vulnerable	CVE Program (cve.org) e CISA ADP
WSO2	Traffic Manager	≥ 4.6.0 and < 4.6.0.11≥ 4.5.0 and < 4.5.0.45	Vulnerable	CVE Program (cve.org) e CISA ADP
WSO2	Universal Gateway	≥ 4.6.0 and < 4.6.0.11≥ 4.5.0 and < 4.5.0.46	Vulnerable	CVE Program (cve.org) e CISA ADP
WSO2	WSO2 Carbon OAuth	≥ 7.0.385 and < 7.0.385.3≥ 7.0.259 and < 7.0.259.34≥ 7.0.26 and < 7.0.26.87≥ 6.13.41 and < 6.13.41.1≥ 6.13.27 and < 6.13.27.10≥ 6.13.19 and < 6.13.19.14≥ 6.13.16 and < 6.13.16.21≥ 6.11.21 and < 6.11.21.94 and 6 more ≥ 6.9.6 and < 6.9.6.29≥ 6.8.0 and < 6.8.0.54≥ 6.4.180 and < 6.4.180.14≥ 6.4.176 and < 6.4.176.30≥ 6.4.111 and < 6.4.111.165≥ 6.4.2 and < 6.4.2.171	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

High

Privileges required

None

User interaction

None

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

Low

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
6.5	CVSS 3.1	Medium	2.2	3.7	ed10eef1-636d-4fbe-9993-6890dfa878f8 via NIST National Vulnerability Database
6.5	CVSS 3.1	Medium	—	—	WSO2 via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:L (score shown at the top: ed10eef1-636d-4fbe-9993-6890dfa878f8)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-613

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).

web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

2026
Source status changed · Received → Awaiting Analysis
Oct 19, 2026 · NIST National Vulnerability Database
Affected products added · wso2/wso2 api control plane, wso2/wso2 universal gateway, wso2/wso2 api manager, wso2/wso2 traffic manager, wso2/wso2 id
Oct 19, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 19, 2026
CVSS changed · 6.5
Oct 19, 2026 · NIST National Vulnerability Database
Source status changed · → Received
Oct 19, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 19, 2026 · Alertas do Telegram
CVE published
Oct 19, 2026 · WSO2

Source activity

Repeated readings are counted rather than listed.

1× References added · Oct 19, 2026 – Oct 19, 2026
1× Official description updated · Oct 19, 2026 – Oct 19, 2026

References

1 on the record

security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4
vendor-advisory, NIST National Vulnerability Database

Elsewhere on this site

WSO2
every CVE for this vendor

CWE-613
other pages naming this weakness

Related CVEs (same products)

Medium CVE-2025-7203 Sensitive Information Disclosure via Management Console and Product Files in Multiple WSO2 Products Allows Retrieval of Credentials 8h
Medium CVE-2025-6623 Stored Cross-Site Scripting via XML Input in Multiple WSO2 Products Allows UI Manipulation and Redirection 8h
Medium CVE-2025-13591 Username Enumeration via Authentication Endpoint in WSO2 Identity Server Allows User Account Discovery 8h
High CVE-2025-10149 Arbitrary Operations via SCIM Endpoints in Multiple WSO2 Products Enables User Account Takeover 8h
Medium CVE-2025-7043 Refresh Token Misuse via Validation Flaw in Multiple WSO2 Products Enables Unauthorized Resource Consumption 8h
Low CVE-2024-4412 Expression Language Injection via User Input in Multiple WSO2 Products Permits Arbitrary Operations 8h

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No FIRST EPSS score.
No fixed version, patch or mitigation documented.
No CISA SSVC assessment.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-13173 is "Improper Token Revocation via Session-Bound Token Flow in Multiple WSO2 Products Allows Unauthorized Access After Session Termination", rated Medium. It affects Api Control Plane (WSO2); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.5 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.