Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By WSO2

  2. · 12 months later

    Published

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-2321, by who scored it
Scored byCVSSScoreVector
WSO2CNA (assigner)3.1Medium5.6CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
NVDNVD · Analyzed3.1Medium5.6CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
EPSS (exploitation in 30 days)
0.24% · top 85% of all CVEs (19 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.6.

Affected products

  • WSO2 · WSO2 API Manager

    • unknown < 3.0.0
    • affected 4.0.0 – < 4.0.0.275
    • affected 4.1.0 – < 4.1.0.153
    • affected 4.2.0 – < 4.2.0.83
  • WSO2 · WSO2 Identity Server

    • unknown < 5.9.0
    • affected 5.11.0 – < 5.11.0.326
    • affected 6.0.0 – < 6.0.0.172
    • affected 6.1.0 – < 6.1.0.130

Affected packages

From reviewed advisories of the GitHub Advisory Database.

What to do

Solution: Follow the instructions given on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2024/WSO2-2024-3213/#solution https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2024/WSO2-2024-3213/#solution

References

References1

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-2321 badge
[![CVE-2024-2321](https://cveledger.app/badge/CVE-2024-2321.svg)](https://cveledger.app/cve/CVE-2024-2321)

Record last updated .