dbcve.org
Api Control PlaneApplication · Wso2

CVE-2025-8591

MEDIUM · 6.1 CVSS v3.1 Published 2026-07-06
Fix available
A fix is available. Upgrade to 2.0.0.404 / 2.0.0.424 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges 6 weeks old

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 software accepts user-supplied input via a URL parameter without adequate output encoding before reflecting it back to the user's browser. This condition allows an attacker to inject malicious script content into pages served by the application. By leveraging this weakness, an attacker can cause the user's browser to redirect to a malicious website, modify the UI of the webpage, or retrieve information from the browser. However, the impact is mitigated by the use of httpOnly flags on session-related cookies, preventing session hijacking.

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 · high confidence

This is a reflected cross-site scripting (XSS) vulnerability where user-supplied input from a URL parameter is reflected back to the user's browser without proper output encoding. An attacker can inject malicious script content to redirect users, modify page UI, or exfiltrate browser data. The impact is partially mitigated by httpOnly flags on session cookies.

MitigationImplement proper output encoding for all user-supplied input before reflecting it in web pages, and consider implementing Content Security Policy (CSP) headers as an additional defense-in-depth measure.

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 Control PlaneApplication
Affected:>= 4.5.0, < 4.5.0.44>= 4.6.0, < 4.6.0.8
Api ManagerApplication
Affected:>= 3.1.0, < 3.1.0.355>= 3.2.0, < 3.2.0.459>= 3.2.1, < 3.2.1.78>= 4.0.0, < 4.0.0.380>= 4.1.0, < 4.1.0.243>= 4.2.0, < 4.2.0.183>= 4.3.0, < 4.3.0.94>= 4.4.0, < 4.4.0.58>= 4.5.0, < 4.5.0.43>= 4.6.0, < 4.6.0.7
Identity ServerApplication
Affected:>= 5.10.0, < 5.10.0.384>= 6.0.0, < 6.0.0.255>= 7.0.0, < 7.0.0.131>= 7.1.0, < 7.1.0.51
Identity Server As Key ManagerApplication
Affected:>= 5.10.0, < 5.10.0.375
Open Banking AmApplication
Affected:>= 2.0.0, < 2.0.0.404
Open Banking IamApplication
Affected:>= 2.0.0, < 2.0.0.424
Traffic ManagerApplication
Affected:>= 4.5.0, < 4.5.0.42>= 4.6.0, < 4.6.0.7
Universal GatewayApplication
Affected:>= 4.5.0, < 4.5.0.42>= 4.6.0, < 4.6.0.7

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. Identify the installed WSO2 product and version
    Locate the product version file in the WSO2 installation directory. Typically found in the PRODUCT_HOME/bin/wso2server.sh or PRODUCT_HOME/repository/conf/etc directory, or check the management console footer for the version number.
    Affected if The product is one of: API Control Plane, API Manager, Identity Server, Identity Server As Key Manager, Open Banking AM, Open Banking IAM, Traffic Manager, or Universal Gateway, AND the version falls within any of the affected ranges listed in the CVE.
  2. Verify the exact version number against affected ranges
    Compare your installed version to the affected version ranges: API Control Plane (4.5.0 to 4.5.0.43, or 4.6.0 to 4.6.0.7); API Manager (3.1.0 to 3.1.0.354, 3.2.0 to 3.2.0.458, 3.2.1 to 3.2.1.77, 4.0.0 to 4.0.0.379, 4.1.0 to 4.1.0.242, 4.2.0 to 4.2.0.182, 4.3.0 to 4.3.0.93, 4.4.0 to 4.4.0.57, 4.5.0 to 4.5.0.42, or 4.6.0 to 4.6.0.6); Identity Server (5.10.0 to 5.10.0.383, 6.0.0 to 6.0.0.254, 7.0.0 to 7.0.0.130, or 7.1.0 to 7.1.0.50); Identity Server As Key Manager (5.10.0 to 5.10.0.374); Open Banking AM (2.0.0 to 2.0.0.403); Open Banking IAM (2.0.0 to 2.0.0.423); Traffic Manager (4.5.0 to 4.5.0.
    Affected if The installed version falls within any of the specified version ranges.
  3. Confirm the web interface is accessible
    Verify the WSO2 management console or API portal web interface is accessible by accessing the base URL of the deployed instance.
    Affected if The web interface is exposed and reachable.
  4. Test for reflected XSS in URL parameters
    Using a browser or HTTP tool, submit a request with a known harmless XSS probe string (such as <script>alert(1)</script>) in various URL parameters and observe if the same string is reflected back in the HTTP response without encoding.
    Affected if The probe string is reflected unescaped in the response HTML, indicating lack of output encoding.

The environment is affected if the installed WSO2 product version falls within any of the specified affected ranges AND the web interface is accessible and reflects URL parameter input without proper 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.

dbcve · scoped
Upgrade available Upgrade to 2.0.0.404 / 2.0.0.424 / 3.1.0.355 or later
Fixed in 2.0.0.4042.0.0.4243.1.0.355
Interim mitigation

Implement proper output encoding for all user-supplied input before reflecting it in web pages, and consider implementing Content Security Policy (CSP) headers as an additional defense-in-depth measure.

Recommended fix High confidence

Upgrade to the minimum fixed version corresponding to your current product version (e.g., Api Control Plane 4.5.0.44, Api Manager 4.0.0.380, Identity Server 7.1.0.51, etc.)

  1. 1. Identify the specific WSO2 product (Api Control Plane, Api Manager, Identity Server, etc.) and current version from the affected version ranges provided.
  2. 2. Determine the appropriate fixed version for your product: Api Control Plane: upgrade to 4.5.0.44 or 4.6.0.8 | Api Manager: upgrade to 3.1.0.355, 3.2.0.459, 3.2.1.78, or 4.0.0.380 | Identity Server: upgrade to 5.10.0.384, 6.0.0.255, 7.0.0.131, or 7.1.0.51 | Identity Server As Key Manager: upgrade to 5.10.0.375 | Open Banking Am: upgrade to 2.0.0.404 | Open Banking Iam: upgrade to 2.0.0.424 | Tra
  3. 3. Review release notes for the target fixed version to understand changes and ensure compatibility with your environment.
  4. 4. Back up your current configuration and data before performing the upgrade.
  5. 5. Download the appropriate fixed version from the WSO2 official distribution repository.
  6. 6. Test the upgrade in a non-production environment to verify the fix and check for any regressions.
  7. 7. Apply the upgrade to production environment during a planned maintenance window.
  8. 8. Verify the XSS vulnerability is remediated by testing that URL parameters are properly encoded and cannot inject malicious scripts.
Caveat Review product-specific release notes; major version upgrades may include breaking changes in configuration or API behavior

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Api Control Plane Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-8591 — 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-8591 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