CVE-2025-7043: Refresh Token Misuse via Validation Flaw in Multiple WSO2 Products Enables Unauthorized Resource Consumption

Severity: medium (CVSS 5.4 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.2% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2026-10-19 · updated 2026-10-28
Weakness: CWE-862

Description

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.

Affected products

WSO2 Api Control Plane: from 4.5.0 before 4.5.0.15 — fixed in 4.5.0.15
WSO2 API Manager: from 3.2.0 before 3.2.0.434; from 3.2.1 before 3.2.1.54; from 4.1.0 before 4.1.0.218; from 4.2.0 before 4.2.0.156; from 4.3.0 before 4.3.0.67; from 4.4.0 before 4.4.0.30 — 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
WSO2 Forgerock Key Manager Component: from 1.0.0 before 1.0.0.3; from 1.0.0 before 1.0.0.4; from 1.1.0 before 1.1.0.2; from 1.1.5 before 1.1.5.3; from 1.1.5 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
WSO2 Universal Gateway: from 4.5.0 before 4.5.0.14 — fixed in 4.5.0.14

How to fix

Upgrade to a fixed version: WSO2 Api Control Plane 4.5.0.15; WSO2 API Manager 3.2.0.434, 3.2.1.54, 4.1.0.218, 4.2.0.156; WSO2 Forgerock Key Manager Component 1.0.0.3, 1.0.0.4, 1.1.0.2, 1.1.5.3; WSO2 Universal Gateway 4.5.0.14. Check the vendor advisory for mitigations.

References

https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4337/

Get alerted when CVE-2025-7043 or the next vulnerability affects your stack