The Management Console and product files expose sensitive data, including remote log server...
Summary
Vulnerability reported (CVE-2025-7203). Confidential information can be exposed externally.
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-7203 has been found.
Confidential information can be exposed externally. CVSS score: 4.9/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "CVE-2025-7203" on the vendor's site.
CVE-2025-7203 — CWE-312 / CVSS v3 4.9
Attack vector: remote (network-reachable) / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-312) has been reported.
Check the vendor advisory for the affected versions.
Severity: Medium (CVSS 4.9/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1
Identify exposureidentify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで影響コンポーネントを特定する。
-
2
Post-deployment verificationverify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
| Ecosystem | Package | Affected | Fixed |
|---|---|---|---|
| WSO2 | WSO2 Universal Gateway |
≥ 4.5.0, < 4.5.0.46 ≥ 4.6.0, < 4.6.0.14 |
4.5.0.46 4.6.0.14 |
| WSO2 | WSO2 Traffic Manager |
≥ 4.5.0, < 4.5.0.45 ≥ 4.6.0, < 4.6.0.14 |
4.5.0.45 4.6.0.14 |
| WSO2 | WSO2 API Control Plane |
≥ 4.5.0, < 4.5.0.47 ≥ 4.6.0, < 4.6.0.15 |
4.5.0.47 4.6.0.15 |
| WSO2 | WSO2 API Manager |
≥ 4.3.0, < 4.3.0.97 ≥ 4.4.0, < 4.4.0.61 ≥ 4.5.0, < 4.5.0.46 ≥ 4.6.0, < 4.6.0.14 |
4.3.0.97 4.4.0.61 4.5.0.46 4.6.0.14 |
| WSO2 | WSO2 Identity Server |
≥ 7.0.0, < 7.0.0.111 ≥ 7.1.0, < 7.1.0.19 |
7.0.0.111 7.1.0.19 |
| WSO2 | WSO2 Carbon Secured HTTP Log4j2 Appender |
≥ 4.9.11, < 4.9.11.4 ≥ 4.9.18, < 4.9.18.2 ≥ 4.10.9, < 4.10.9.2 ≥ 4.10.19, < 4.10.19.1 |
4.9.11.4 4.9.18.2 4.10.9.2 4.10.19.1 |
| WSO2 | WSO2 Carbon Logging Services |
≥ 4.9.11, < 4.9.11.4 ≥ 4.9.18, < 4.9.18.2 ≥ 4.10.9, < 4.10.9.2 ≥ 4.10.19, < 4.10.19.1 |
4.9.11.4 4.9.18.2 4.10.9.2 4.10.19.1 |
| WSO2 | WSO2 Carbon Identity API Server Configs V1 |
≥ 1.2.176, < 1.2.176.16 ≥ 1.3.83, < 1.3.83.7 |
1.2.176.16 1.3.83.7 |
Original description The description as published by the source.
The Management Console and product files expose sensitive data, including remote log server credentials, truststore passwords, and keystore passwords, in plain text. This occurs because the system does not sufficiently protect or obscure these credentials when the remote logging feature is enabled.
An attacker with administrative access to the Management Console or direct access to product files can retrieve these sensitive credentials. This allows for potential manipulation of log entries and compromise of the integrity and confidentiality of the remote log server.
Source: NIST National Vulnerability Database NVD GitHub Advisory
References
- web security.docs.wso2.com
- web nvd.nist.gov
- web security.docs.wso2.com
- web github.com