Quick answers
- Is CVE-2025-6508 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-6508 being exploited in the wild.
- How severe is CVE-2025-6508?
- Medium severity, with a CVSS score of 4.3, published 6 August 2026.
- Which products and versions are affected?
- Wso2 API Manager 4.1.0, 4.2.0.
- Is there a fix for CVE-2025-6508?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2025-6508 attacked?
- It is attacked over the network.
- Am I affected by CVE-2025-6508?
- Check whether you run Wso2 API Manager at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a UI misrepresentation flaw in the Swagger UI Try-out console integrated within the API Publisher documentation module. The root cause is insecure handling of external Swagger API definition URLs, which allows an attacker to supply a malicious URL that overrides the legitimate API definitions stored in the Publisher portal. The attack requires user interaction (UI:R) and network reachability with no prior authentication needed (PR:N). An attacker can craft a phishing link or social engineering attack that directs a user to access the API Publisher with a specially crafted parameter pointing to a malicious Swagger definition URL, causing the console to load attacker-controlled API specifications. This could lead to unintended API requests sent to attacker infrastructure or disclosure of sensitive data. WSO2 provides fixes via update levels: API Manager 4.2.0 requires update 183, and 4.1.0 requires update 212.
Affected products
- WSO2 API Manager 4.1.0, 4.2.0
Timeline
- 2026-05-03: disclosed
- 2026-08-06: published