Strix
74.4K

CVE-2025-7043

MEDIUMCVSS 5.4/10EPSS 0.18%

Last modified

CVE-2025-7043 is a medium-severity vulnerability rated 5.4/10 on the CVSS scale. 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. EPSS estimates a 0.18% chance of exploitation in the next 30 days.

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.

Metrics

CVSS 3.1
5.4/10

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N

EPSS Probability
0.18%

8.1th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
WSO2WSO2 API Manager< 3.2.0; >= 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; >= 4.5.0, < 4.5.0.14
WSO2WSO2 Universal Gateway< 4.5.0; >= 4.5.0, < 4.5.0.14
WSO2WSO2 API Control Plane< 4.5.0; >= 4.5.0, < 4.5.0.15
WSO2Forgerock 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

References

Timeline

Published
Last Modified
Status
Awaiting Analysis

Frequently Asked Questions

What is CVE-2025-7043?
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.
How severe is CVE-2025-7043?
CVE-2025-7043 has a CVSS score of 5.4/10 (MEDIUM severity). The EPSS model estimates a 0.18% probability of exploitation in the next 30 days.
How do I fix CVE-2025-7043?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2025

View all 2025CVEs →

Are you affected by CVE-2025-7043?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST