dbcve.org
Api ManagerApplication · Wso2

CVE-2025-6024

MEDIUM · 6.1 CVSS v3.1 Published 2026-04-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The authentication endpoint fails to encode user-supplied input before rendering it in the web page, allowing for script injection. An attacker can leverage this by injecting malicious scripts into the authentication endpoint. This can result in the user's browser being redirected to a malicious website, manipulation of the web page's user interface, or the retrieval of information from the browser. However, session hijacking is not possible due to the httpOnly flag protecting session-related cookies.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Reflected cross-site scripting (XSS) vulnerability in the authentication endpoint where user-supplied input is not properly encoded before being rendered in the response page. Attackers can inject malicious JavaScript that executes in the victim's browser, enabling page redirection, UI manipulation, or sensitive data exfiltration via browser APIs.

MitigationImplement proper output encoding/escaping for all user-supplied data rendered in HTML context at the authentication endpoint. Apply context-appropriate encoding (HTML, URL, JavaScript) based on where the data is inserted into the page.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Api ManagerApplication
Affected:= 3.1.0= 3.2.0= 3.2.1= 4.0.0= 4.1.0
Identity ServerApplication
Affected:= 5.10.0= 5.11.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm WSO2 product installation
    Locate the WSO2 installation directory. For API Manager, look for the 'wso2am' folder or check for 'wso2server.sh' or 'wso2server.bat' script. For Identity Server, look for 'wso2is' folder or 'wso2server' script. Check for the presence of 'repository/components' directory containing the product binaries.
    Affected if The product is WSO2 API Manager 3.1.0, 3.2.0, 3.2.1, 4.0.0, or 4.1.0; OR WSO2 Identity Server 5.10.0 or 5.11.0
  2. Determine installed product version
    Open the 'repository/components/plugins' directory and locate the core JAR file (typically 'org.wso2.carbon.core_*.jar'). Alternatively, check the 'carbon.xml' configuration file in 'repository/conf' for the 'ServerVersion' property. You can also view the product splash page or check the 'product-version' in the server startup logs.
    Affected if The installed version matches exactly: 3.1.0, 3.2.0, 3.2.1, 4.0.0, or 4.1.0 for API Manager; or 5.10.0 or 5.11.0 for Identity Server
  3. Verify authentication endpoint is accessible
    Access the default authentication endpoint URL. For API Manager, this is typically 'https://<host>:9443/authenticationendpoint/login.do'. For Identity Server, it is typically 'https://<host>:9443/login.do'. Confirm the endpoint responds with a login page.
    Affected if The authentication endpoint is exposed and accessible, meaning user input can be submitted to this endpoint
  4. Check for XSS vulnerability in authentication endpoint
    Send a crafted request to the authentication endpoint with a test payload in the query parameters (such as '<script>alert(1)</script>') and inspect the response HTML to see if the payload is reflected without proper encoding. Use browser developer tools or a proxy to view the raw HTTP response.
    Affected if User-supplied input in authentication endpoint parameters is reflected in the response without HTML encoding (unescaped '<' and '>' characters visible in the page source)

You are affected if you have WSO2 API Manager (exact versions 3.1.0, 3.2.0, 3.2.1, 4.0.0, 4.1.0) or WSO2 Identity Server (exact versions 5.10.0, 5.11.0) installed AND the authentication endpoint is accessible and reflects user input without encoding.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper output encoding/escaping for all user-supplied data rendered in HTML context at the authentication endpoint. Apply context-appropriate encoding (HTML, URL, JavaScript) based on where the data is inserted into the page.

Fix this in Api Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-6024 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-6024 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data