The ForgeRock client fails to correctly validate refresh tokens. This allows a refresh token to...
Summary
Vulnerability reported (CVE-2025-7043). Risk of unauthorized operations or information disclosure.
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-7043 has been found.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "CVE-2025-7043" on the vendor's site.
CVE-2025-7043 — CWE-862 / CVSS v3 5.4
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-862) has been reported.
Check the vendor advisory for the affected versions.
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1
Identify exposureidentify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで影響コンポーネントを特定する。
-
2
Post-deployment verificationverify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
| Ecosystem | Package | Affected | Fixed |
|---|---|---|---|
| WSO2 | WSO2 API Manager |
≥ 3.2.0, < 3.2.0.434 ≥ 3.2.1, < 3.2.1.54 ≥ 4.1.0, < 4.1.0.218 ≥ 4.2.0, < 4.2.0.156 ≥ 4.3.0, < 4.3.0.67 ≥ 4.4.0, < 4.4.0.30 +1 more |
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 | WSO2 Universal Gateway |
≥ 4.5.0, < 4.5.0.14 |
4.5.0.14 |
| WSO2 | WSO2 API Control Plane |
≥ 4.5.0, < 4.5.0.15 |
4.5.0.15 |
| WSO2 | Forgerock Key Manager Component |
≥ 1.0.0, < 1.0.0.3 ≥ 1.0.0, < 1.0.0.4 ≥ 1.1.0, < 1.1.0.2 ≥ 1.1.5, < 1.1.5.3 ≥ 1.1.5, < 1.1.5.4 |
1.0.0.3 1.0.0.4 1.1.0.2 1.1.5.3 1.1.5.4 |
Original description The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
References
- web security.docs.wso2.com
- web nvd.nist.gov
- web security.docs.wso2.com
- web github.com