CVE-2025-12737 — OS Command Injection in WSO2 Api Control Plane
The administrative operations within the Carbon Console do not adequately validate specific user-supplied input. This oversight allows a malicious actor with administrative privileges to inject and execute arbitrary code remotely. Successful exploitation enables a threat actor with administrative privileges and Carbon Console access to execute remote arbitrary code through specific administrative operations, leading to a complete compromise of the affected system.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — security.docs.wso2.com (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (WSO2 Api Control Plane, WSO2 Api Manager, WSO2 Identity Server…).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| WSO2 | Api Control Plane | version 4.6.0≥ 4.5.0 and < 4.5.0.36 | Vulnerable | NIST National Vulnerability Database |
| WSO2 | Api Manager |
version 4.6.0≥ 4.5.0 and < 4.5.0.35≥ 4.4.0 and < 4.4.0.52≥ 4.3.0 and < 4.3.0.88≥ 4.2.0 and < 4.2.0.176≥ 4.1.0 and < 4.1.0.236≥ 4.0.0 and < 4.0.0.373≥ 3.2.1 and < 3.2.1.73 and 2 more≥ 3.2.0 and < 3.2.0.453≥ 3.1.0 and < 3.1.0.349 |
Vulnerable | NIST National Vulnerability Database |
| WSO2 | Identity Server | version 7.2.0≥ 5.10.0 and < 5.10.0.378≥ 5.11.0 and < 5.11.0.425≥ 6.0.0 and < 6.0.0.252≥ 6.1.0 and < 6.1.0.253≥ 7.0.0 and < 7.0.0.130≥ 7.1.0 and < 7.1.0.38 | Vulnerable | NIST National Vulnerability Database |
| WSO2 | Identity Server As Key Manager | ≥ 5.10.0 and < 5.10.0.369 | Vulnerable | NIST National Vulnerability Database |
| WSO2 | Open Banking Am | ≥ 2.0.0 and < 2.0.0.398 | Vulnerable | NIST National Vulnerability Database |
| WSO2 | Open Banking Iam | ≥ 2.0.0 and < 2.0.0.418 | Vulnerable | NIST National Vulnerability Database |
| WSO2 | Traffic Manager | version 4.6.0≥ 4.5.0 and < 4.5.0.34 | Vulnerable | NIST National Vulnerability Database |
| WSO2 | Universal Gateway | version 4.6.0≥ 4.5.0 and < 4.5.0.34 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 8.4 | CVSS 3.1 | High | 1.7 | 6.0 | ed10eef1-636d-4fbe-9993-6890dfa878f8 via NIST National Vulnerability Database |
CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H (score shown at the top: ed10eef1-636d-4fbe-9993-6890dfa878f8) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Look for parameters with command/query metacharacters and unexpected child processes of the service.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Fix documented
- CVSS changed · 8.4
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
1 on the record
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2024-8122 Potential brute force vulnerability due to non-expiring SMS OTPs 7d
- Low CVE-2025-13166 Username Enumeration via SMS OTP Flow in WSO2 Identity Server Allows User Account Discovery Sep 15, 2026
- High CVE-2026-3416 Use of Insufficiently Random Values in WSO2 Api Control Plane Sep 3, 2026
- High CVE-2026-3415 XML External Entity (XXE) Injection via Schema Validation in Multiple WSO2 Products Allows File Reading and Denial of Service Aug 6, 2026
- Critical CVE-2026-3418 Arbitrary File Upload via System REST API in Multiple WSO2 Products Allows Remote Code Execution Aug 6, 2026
- Medium CVE-2025-12317 Improper Token Revocation via SOAP Services in Multiple WSO2 Products Allows Retained Access Privileges Aug 6, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No FIRST EPSS score.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-12737 is "OS Command Injection in WSO2 Api Control Plane", rated High. It affects Api Control Plane (WSO2); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.4 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.