Skip to content
Noroxi
CVE-2024-2321· NVD / CVE Program· CNA WSO2

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

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.

MediumCVSS 5.6 · v3.1—No exploit No fix recorded
Published
Feb 27, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 14th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.6 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.6
CNA · WSO2
5.6
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
wso2api manager
wso2identity server

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • wso2 api manager4.0.0
  • wso2 api manager4.1.0
  • wso2 api manager4.2.0
  • wso2 identity server5.11.0
  • wso2 identity server6.0.0
  • wso2 identity server6.1.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (WSO2). Independent of NVD's CPE analysis and usually ahead of it.

  • WSO2 WSO2 API Manager

    • before 3.0.0unknown
    • 4.0.0 and later · before 4.0.0.275affected
    • 4.1.0 and later · before 4.1.0.153affected
    • 4.2.0 and later · before 4.2.0.83affected

  • WSO2 WSO2 Identity Server

    • before 5.9.0unknown
    • 5.11.0 and later · before 5.11.0.326affected
    • 6.0.0 and later · before 6.0.0.172affected
    • 6.1.0 and later · before 6.1.0.130affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Mavenorg.wso2.am:am-parentfrom 4.0.0-beta · up to and including 4.0.0—
Mavenorg.wso2.am:am-parentfrom 4.1.0-alpha · up to and including 4.1.0—
Mavenorg.wso2.am:am-parentfrom 4.2.0-beta · up to and including 4.2.0—
Mavenorg.wso2.is:identity-server-parentfrom 5.11.0-alpha · up to and including 5.11.0—
Mavenorg.wso2.is:identity-server-parentfrom 6.0.0-alpha3 · up to and including 6.0.0—
Mavenorg.wso2.is:identity-server-parentfrom 6.1.0-beta · up to and including 6.1.0—

Same product

wso2: all records

Other highest-scoring records for the same primary product.

  • CVE-2022-29464Certain WSO2 products allow unrestricted file upload with resultant remote code execution.KEV
    99Now
  • CVE-2020-24589The Management Console in WSO2 API Manager through 3.1.0 and API Microgateway 2.2.0 allows XML External Entity injection (XXE) attacks.
    44Plan
  • CVE-2026-2053Unauthenticated Server-Side Request Forgery via WS-Addressing in WSO2 API Manager
    40Plan
  • CVE-2020-13226WSO2 API Manager 3.0.0 does not properly restrict outbound network access from a Publisher node, opening up the possibility of SSRF to this
    40Plan
  • CVE-2024-6914Incorrect Authorization in Multiple WSO2 Products via Account Recovery SOAP Admin Service Leading to Account Takeover
    39Monitor
  • CVE-2021-42646XML External Entity (XXE) vulnerability in the file based service provider creation feature of the Management Console in WSO2 API Manager 2.
    37Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2024-691484 days apartIncorrect Authorization in Multiple WSO2 Products via Account Recovery SOAP Admin Service Leading to Account Takeover
    39Monitor
  • CVE-2023-6837440 days apartIncorrect Authorization in Multiple WSO2 Products via Federated Authentication with JIT Provisioning Leading to User Impersonation
    32Monitor
  • CVE-2024-709692 days apartPrivilege Escalation in Multiple WSO2 Products via SOAP Admin Service Due to Business Logic Flaw
    21Monitor
  • CVE-2024-709792 days apartIncorrect Authorization in Multiple WSO2 Products via SOAP Admin Service Allowing Unauthorized User Signup
    17Monitor
  • CVE-2024-3511116 days apartIncorrect Authorization in Multiple WSO2 Products Allows Unauthorized Access to Registry Versioned Files
    17Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
low · data can be read
Integrity
low · data or configuration can be modified
Availability
low · the service can be disrupted
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
Low
Availability impact
Low

Weakness class (CWE)

CWE-863 · Incorrect Authorization

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records