WSO2 incorrect authorization vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2024-2321: 0.24% estimated exploitation activity in the next 30 days; percentile 15.29 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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 by the source

27 Feb 2025, 06:30 UTC

Last modified by the source

3 Mar 2025, 19:50 UTC

Source last checked

26 Oct 2026, 16:35 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-6qjp-wm6g-m32r

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-2321

Advisory: WSO2 incorrect authorization vulnerability
IDs: CVE-2024-2321, GHSA-6qjp-wm6g-m32r
Record: https://patchnext.com/advisories/cve-2024-2321 (revision 1, source checked 26 Oct 2026, 16:35 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.wso2.am:am-parent: affected >= 4.2.0-beta, <= 4.2.0; >= 4.1.0-alpha, <= 4.1.0; >= 4.0.0-beta, <= 4.0.0
- Maven org.wso2.is:identity-server-parent: affected >= 6.1.0-beta, <= 6.1.0; >= 6.0.0-alpha3, <= 6.0.0; >= 5.11.0-alpha, <= 5.11.0

## Suggested inspection (read-only)
- Maven org.wso2.am:am-parent: check the installed version with your package manager.
- Maven org.wso2.is:identity-server-parent: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.wso2.am:am-parent, org.wso2.is:identity-server-parent.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-6qjp-wm6g-m32r (GitHub-reviewed advisory GHSA-6qjp-wm6g-m32r lists affected ranges: Maven org.wso2.am:am-parent >=4.2.0-beta =4.1.0-alpha =4.0.0-beta =6.1.0-beta =6.0.0-alpha3 =5.11.0-alpha <=5.11.0)

Commands are suggestions: review each one before running it.