Security Advisory WSO2-2025-4369/CVE-2025-7203

Published: 2026-05-03

Version: 1.0.0

Severity: Medium

CVSS Score: 4.9 (CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N)

CVE IDs: CVE-2025-7203


AFFECTED PRODUCTS

  • WSO2 API Control Plane: 4.6.0, 4.5.0
  • WSO2 API Manager: 4.6.0, 4.5.0, 4.4.0, 4.3.0
  • WSO2 Identity Server: 7.1.0, 7.0.0
  • WSO2 Traffic Manager: 4.6.0, 4.5.0
  • WSO2 Universal Gateway: 4.6.0, 4.5.0

OVERVIEW

Potential sensitive information disclosure when the remote log is enabled.

DESCRIPTION

Administrators can view sensitive data such as configured remote log server credentials, truststore password, and keystore password in plain text from the Management Console UI, the API, and in the product files.

IMPACT

To exploit this vulnerability, a malicious actor must either possess a valid user account for the Management Console with admin access or have access to the product files. With such access, they could retrieve the credentials of the remote logging server and potentially manipulate log entries, thereby compromising the integrity of the remote log server.

SOLUTION

Community Users (Open Source)

Apply the relevant fixes to your product using the public fix(es) provided below.

If applying the fix or update is not feasible, migrate to the latest unaffected version of the respective WSO2 product(s).

Support Subscription Holders

Update your product to the specified update level, or to a higher update level, to mitigate the identified vulnerability.

Info

WSO2 Support Subscription Holders may use WSO2 Updates in order to apply the fix.

Product Name Product Version Update Level
WSO2 API Control Plane 4.6.0 15
WSO2 API Control Plane 4.5.0 47
WSO2 API Manager 4.6.0 14
WSO2 API Manager 4.5.0 46
WSO2 API Manager 4.4.0 61
WSO2 API Manager 4.3.0 97
WSO2 Identity Server 7.1.0 19
WSO2 Identity Server 7.0.0 111
WSO2 Traffic Manager 4.6.0 14
WSO2 Traffic Manager 4.5.0 45
WSO2 Universal Gateway 4.6.0 14
WSO2 Universal Gateway 4.5.0 46

After apply the provided update or PR to the affected versions of the products. Along with the update, it is required to apply the following configuration into the deployment.toml to completely avoid the vulnerable behaviour from the deployment.

[remote_logging]
encrypt_secrets=true
hide_secrets=true

In addition, we strongly recommend rotating the remote log server credentials, truststore password, and keystore password to mitigate the risk of future security breaches.