Skip to content
Noroxi
NVD / CVE Program· CNA WSO2

CVE-2024-2321: Incorrect Authorization in Multiple WSO2 Products Allows API Access via Refresh Token

MediumCVSS 5.6 · v3.1—No exploit No fix recorded

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
  • 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.
  • According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Feb 27, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 15th percentile

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.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-2321

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for wso2 records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
wso2api manager
wso2identity server

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
Affected versions · NVD (6)

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

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

Published before and after this one in the same product

  • ← EarlierCVE-2023-6839Dec 15, 2023 · Due to improper error handling, a REST API resource could expose a server side error containing an internal WSO2 specific package name in…
    21Monitor
  • ← EarlierCVE-2023-6911Dec 18, 2023 · Multiple WSO2 products have been identified as vulnerable due to improper output encoding, a Stored Cross Site Scripting (XSS) attack can…
    19Monitor
  • Later →CVE-2024-5848Feb 27, 2025 · Reflected Cross-Site Scripting (XSS) in Multiple WSO2 Products Due to Improper Input Validation
    24Monitor

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.

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

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.

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.

References

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

All records