cve.bz

CVE-2025-7043 wso2: Missing Authorization

5.4 mediumEPSS 0.2%

Medium (5.4) in wso2. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

5.4 medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
EPSS
0.2% (unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 8th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-28. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-862 Missing Authorization
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2025-7043 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-7043?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-7043?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-7043 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • wso2:forgerock key manager component
  • wso2:wso2 api control plane
  • wso2:wso2 api manager
  • wso2:wso2 universal gateway

Versions

From the CNA's record in the CVE List.

ProductAffected
WSO2 API Managerfrom 3.2.0 before 3.2.0.434
WSO2 API Managerfrom 3.2.1 before 3.2.1.54
WSO2 API Managerfrom 4.1.0 before 4.1.0.218
WSO2 API Managerfrom 4.2.0 before 4.2.0.156
WSO2 API Managerfrom 4.3.0 before 4.3.0.67
WSO2 API Managerfrom 4.4.0 before 4.4.0.30
WSO2 API Managerfrom 4.5.0 before 4.5.0.14
WSO2 Universal Gatewayfrom 4.5.0 before 4.5.0.14
WSO2 API Control Planefrom 4.5.0 before 4.5.0.15
WSO2 Forgerock Key Manager Componentfrom 1.0.0 before 1.0.0.3
WSO2 Forgerock Key Manager Componentfrom 1.0.0 before 1.0.0.4
WSO2 Forgerock Key Manager Componentfrom 1.1.0 before 1.1.0.2
WSO2 Forgerock Key Manager Componentfrom 1.1.5 before 1.1.5.3
WSO2 Forgerock Key Manager Componentfrom 1.1.5 before 1.1.5.4

Attack patterns (CAPEC)

  • CAPEC-665 Exploitation of Thunderbolt Protection Flaws Likelihood: Low · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON