Refresh tokens accepted as access tokens in multiple WSO2 products
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- High
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- Low · Low · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-862.
Summary
Several WSO2 products, including WSO2 API Manager, WSO2 Universal Gateway, WSO2 API Control Plane and Forgerock Key Manager Component, are affected. The ForgeRock client does not correctly validate refresh tokens, so a refresh token is accepted as a valid access token (CWE-862). An attacker who obtains a stolen or exposed refresh token can use it to access protected resources without the client credentials that the normal flow requires.
Written with Claude Haiku 5.5 from the sources below · 2026-10-29
Description from the CNA
The ForgeRock client fails to correctly validate refresh tokens. This allows a refresh token to be treated as a valid access token, enabling its use for consuming protected resources. This bypasses the intended security control that requires valid client credentials in addition to a refresh token to obtain a new access token. An attacker who obtains a stolen or exposed refresh token can leverage this vulnerability to directly access protected resources. This is possible because the standard security flow requiring client credentials to exchange a refresh token for an access token is circumvented.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| WSO2 | WSO2 API Manager | 3.2.0 to before 3.2.0.434; 3.2.1 to before 3.2.1.54; 4.1.0 to before 4.1.0.218; 4.2.0 to before 4.2.0.156; 4.3.0 to before 4.3.0.67; 4.4.0 to before 4.4.0.30; 4.5.0 to before 4.5.0.14 | 3.2.0.434, 3.2.1.54, 4.1.0.218, 4.2.0.156, 4.3.0.67, 4.4.0.30, 4.5.0.14 | Patch available | CNA |
| WSO2 | WSO2 Universal Gateway | 4.5.0 to before 4.5.0.14 | 4.5.0.14 | Patch available | CNA |
| WSO2 | WSO2 API Control Plane | 4.5.0 to before 4.5.0.15 | 4.5.0.15 | Patch available | CNA |
| WSO2 | Forgerock Key Manager Component | 1.0.0 to before 1.0.0.3; 1.0.0 to before 1.0.0.4; 1.1.0 to before 1.1.0.2; 1.1.5 to before 1.1.5.3; 1.1.5 to before 1.1.5.4 | 1.0.0.3, 1.0.0.4, 1.1.0.2, 1.1.5.3, 1.1.5.4 | Patch available | CNA |
- WSO2 API Manager VendorWSO2 Affected 3.2.0 to before 3.2.0.434; 3.2.1 to before 3.2.1.54; 4.1.0 to before 4.1.0.218; 4.2.0 to before 4.2.0.156; 4.3.0 to before 4.3.0.67; 4.4.0 to before 4.4.0.30; 4.5.0 to before 4.5.0.14 Fixed in 3.2.0.434, 3.2.1.54, 4.1.0.218, 4.2.0.156, 4.3.0.67, 4.4.0.30, 4.5.0.14 Patch available CNA
- WSO2 Universal Gateway VendorWSO2 Affected 4.5.0 to before 4.5.0.14 Fixed in 4.5.0.14 Patch available CNA
- WSO2 API Control Plane VendorWSO2 Affected 4.5.0 to before 4.5.0.15 Fixed in 4.5.0.15 Patch available CNA
- Forgerock Key Manager Component VendorWSO2 Affected 1.0.0 to before 1.0.0.3; 1.0.0 to before 1.0.0.4; 1.1.0 to before 1.1.0.2; 1.1.5 to before 1.1.5.3; 1.1.5 to before 1.1.5.4 Fixed in 1.0.0.3, 1.0.0.4, 1.1.0.2, 1.1.5.3, 1.1.5.4 Patch available CNA
Remediation
Upgrade WSO2 API Manager to 3.2.0.434, 3.2.1.54, 4.1.0.218, 4.2.0.156, 4.3.0.67, 4.4.0.30 or 4.5.0.14. Upgrade WSO2 Universal Gateway to 4.5.0.14, WSO2 API Control Plane to 4.5.0.15 and Forgerock Key Manager Component to 1.0.0.3, 1.0.0.4, 1.1.0.2, 1.1.5.3 or 1.1.5.4.
Written with Claude Haiku 5.5 from the sources below · 2026-10-29
- Fix · CNA WSO2 API Manager (WSO2) Fixed in 3.2.0.434, 3.2.1.54, 4.1.0.218, 4.2.0.156, 4.3.0.67, 4.4.0.30, 4.5.0.14
- Fix · CNA WSO2 Universal Gateway (WSO2) Fixed in 4.5.0.14
- Fix · CNA WSO2 API Control Plane (WSO2) Fixed in 4.5.0.15
- Fix · CNA Forgerock Key Manager Component (WSO2) Fixed in 1.0.0.3, 1.0.0.4, 1.1.0.2, 1.1.5.3, 1.1.5.4
Timeline
- 2026-10-19 Threatist record created from CVE-2025-7043
- 2026-10-20 Alias added: GHSA-vp4v-gjpc-c4x6
- 2026-10-21 Priority changed: MEDIUM → LOW
- 2026-10-28 CISA SSVC decision points changed
References
More WSO2 vulnerabilities
- TI-2026-04755 Authentication Bypass via JWT Algorithm Mismatch in Multiple WSO2 Products Allows Account Takeover KEVCVSS 3.1CRITICAL 10.0
- TI-2022-11928 Certain WSO2 products allow unrestricted file upload with resultant remote code execution. KEVCVSS 3.1CRITICAL 9.8
- TI-2022-18808 An issue was discovered in WSO2 Enterprise Integrator 6.4.0. CVSS 3.1MEDIUM 6.1
- TI-2020-15069 The Management Console in WSO2 API Manager through 3.1.0 and API Microgateway 2.2.0… CVSS 3.1CRITICAL 9.1
- TI-2023-15163 A reflected cross-site scripting (XSS) vulnerability in /authenticationendpoint/login.do… CVSS 3.1MEDIUM 6.1
- TI-2022-04130 WSO2 carbon-registry Advanced Search advancedSearchForm-ajaxprocessor.jsp cross site scripting CVSS 3.1MEDIUM 6.1
Sources
- CVE-2025-7043 · CVE Program
- CVE-2025-7043 · NVD
- FIRST EPSS
- GHSA-vp4v-gjpc-c4x6 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences