vulntracker.iovulntracker.io
© 2026 vulntracker.io

CVE-2024-2321

Incorrect Authorization in Multiple WSO2 Products Allows API Access via Refresh Token

MEDIUM
5.6
CVSS Score
Published: February 27, 2025 at 04:08 AM UTC
Updated: June 17, 2026 at 07:24 AM UTC
2 products affected across 1 vendorAPI ManagerIdentity Server

Using WSO2 API Manager by WSO2?

Get instant alerts when new vulnerabilities affect WSO2 API Manager - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Start FreeSign In
Severity
MEDIUM5.6
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

An incorrect authorization vulnerability exists in multiple WSO2 products, allowing protected APIs to be accessed directly using a refresh token instead of the expected access token. Due to improper authorization checks and token mapping, session cookies are not required for API access, potentially enabling unauthorized operations. Exploitation requires an attacker to obtain a valid refresh token of an admin user. Since refresh tokens generally have a longer expiration time, this could lead to prolonged unauthorized access to API resources, impacting data confidentiality and integrity.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

API Manager· WSO2
95%
4.0.0 ≤ v < 4.0.0.2754.1.0 ≤ v < 4.1.0.1534.2.0 ≤ v < 4.2.0.834.0.04.1.04.2.0
Affected range stops below 4.0.0.275, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.1.0.153, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.2.0.83, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 3.0.0 (unknown)
Identity Server· WSO2
95%
5.11.0 ≤ v < 5.11.0.3266.0.0 ≤ v < 6.0.0.1726.1.0 ≤ v < 6.1.0.1305.11.06.0.06.1.0
Affected range stops below 5.11.0.326, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.0.0.172, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.1.0.130, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.9.0 (unknown)

Remediation

No guide yet

No 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/2024/WSO2-2024-3213/

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.6MEDIUMWSO2
Attack Vector
NETWORK
Complexity
HIGH
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
LOW
Integrity
LOW
Availability
LOW
Vector?

Quick Info

StatusANALYZED
CWE
CWE-863

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.

Create accountSign in
Free plan, no card