CVE-2024-8995Authorization Code issued for Deleted User reuse in Multiple WSO2 Products Allows Unauthorized Access
- 4.9MediumCVSS base score
- 0.19%Exploitation in 30 daysEPSS · top 92% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
Unused authorization codes issued to deleted users are not being properly invalidated or removed from the system. This allows for the persistence of these codes, enabling them to be potentially reused. If an attacker possesses both the authorization code and the associated client credentials (client ID and client secret), they can leverage these unused codes to obtain access tokens on behalf of users who have already been deleted. This may lead to unauthorized access to sensitive resources and services, contingent on the scopes originally authorized for the compromised authorization code.
Timeline
ID reserved
By WSO2
- 23 months later
· 23 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
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| WSO2CNA (assigner) | 3.1 | Medium4.9 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N |
| NVDNVD · Analyzed | 3.1 | Medium4.9 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N |
- EPSS (exploitation in 30 days)
- 0.19% · top 92% of all CVEs (17 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 4.9.
Affected products
- unknown < 3.1.0
- affected 3.1.0 – < 3.1.0.320
- affected 3.2.0 – < 3.2.0.413
- affected 3.2.1 – < 3.2.1.90
- affected 4.0.0 – < 4.0.0.334
- affected 4.1.0 – < 4.1.0.255
- affected 4.2.0 – < 4.2.0.195
- affected 4.3.0 – < 4.3.0.106
- affected 4.4.0 – < 4.4.0.70
- affected 4.5.0 – < 4.5.0.55
- affected 4.6.0 – < 4.6.0.19
- affected 4.5.0 – < 4.5.0.54
- affected 4.6.0 – < 4.6.0.19
- affected 4.5.0 – < 4.5.0.56
- affected 4.6.0 – < 4.6.0.20
- affected 4.5.0 – < 4.5.0.55
- affected 4.6.0 – < 4.6.0.19
- unknown < 2.0.0
- affected 2.0.0 – < 2.0.0.369
- unknown < 5.10.0
- affected 5.10.0 – < 5.10.0.345
- affected 5.11.0 – < 5.11.0.395
- affected 6.0.0 – < 6.0.0.229
- affected 6.1.0 – < 6.1.0.208
- unknown < 2.0.0
- affected 2.0.0 – < 2.0.0.389
WSO2 · WSO2 Identity Server as Key Manager
- unknown < 5.10.0
- affected 5.10.0 – < 5.10.0.338
- affected 6.4.2 – < 6.4.2.154
- affected 6.4.111 – < 6.4.111.131
- affected 6.4.176 – < 6.4.176.35
- affected 6.4.180 – < 6.4.180.17
- affected 6.8.0 – < 6.8.0.46
- affected 6.9.6 – < 6.9.6.34
- affected 6.11.21 – < 6.11.21.59
- affected 6.13.16 – < 6.13.16.27
- affected 6.13.19 – < 6.13.19.19
- affected 6.13.27 – < 6.13.27.15
- affected 6.13.41 – < 6.13.41.4
- unaffected 6.11.53 – ≤ *
What to do
Solution: Follow the instructions given on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-2753/#solution
References
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2024-55706 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2024-8995)Record last updated .