NVD / CVE Program· CNA WSO2

CVE-2025-12737: Arbitrary Code Execution via Administrative Operations in Multiple WSO2 Products Allows Remote Code Execution

Noroxi assessment

Priority: Monitor (action score 33/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.37% (FIRST EPSS).
Someone on the same network segment can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 8.4 · v3.1—No exploit No fix recorded

EUVD-2025-210842

Published: Sep 3, 2026
Updated: Oct 19, 2026
EPSS: 0.3% · 31th percentile
CWE: CWE-78

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 33 / 40 · 8.4 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.3%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · WSO2: 8.4; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
wso2	api control plane	cpe:2.3:a:wso2:api_control_plane
wso2	api manager	cpe:2.3:a:wso2:api_manager
wso2	identity server	cpe:2.3:a:wso2:identity_server
wso2	identity server as key manager	cpe:2.3:a:wso2:identity_server_as_key_manager
wso2	open banking am	cpe:2.3:a:wso2:open_banking_am
wso2	open banking iam	cpe:2.3:a:wso2:open_banking_iam
wso2	traffic manager	cpe:2.3:a:wso2:traffic_manager
wso2	universal gateway	cpe:2.3:a:wso2:universal_gateway

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

wso2 api control plane4.5.0 and later · before 4.5.0.36
wso2 api control plane4.6.0
wso2 api manager3.1.0 and later · before 3.1.0.349
wso2 api manager3.2.0 and later · before 3.2.0.453
wso2 api manager3.2.1 and later · before 3.2.1.73
wso2 api manager4.0.0 and later · before 4.0.0.373
wso2 api manager4.1.0 and later · before 4.1.0.236
wso2 api manager4.2.0 and later · before 4.2.0.176
wso2 api manager4.3.0 and later · before 4.3.0.88
wso2 api manager4.4.0 and later · before 4.4.0.52
wso2 api manager4.5.0 and later · before 4.5.0.35
wso2 api manager4.6.0
wso2 identity server5.10.0 and later · before 5.10.0.378
wso2 identity server5.11.0 and later · before 5.11.0.425
wso2 identity server6.0.0 and later · before 6.0.0.252
wso2 identity server6.1.0 and later · before 6.1.0.253
wso2 identity server7.0.0 and later · before 7.0.0.130
wso2 identity server7.1.0 and later · before 7.1.0.38
wso2 identity server7.2.0
wso2 identity server as key manager5.10.0 and later · before 5.10.0.369

Versions reported by the vendor

Affected version ranges reported by the assigning authority (WSO2). Independent of NVD's CPE analysis and usually ahead of it.

WSO2 WSO2 API Control Plane
- 4.5.0 and later · before 4.5.0.36affected
- 4.6.0 and later · before 4.6.0.1affected
WSO2 WSO2 API Manager
- before 3.1.0unknown
- 3.1.0 and later · before 3.1.0.349affected
- 3.2.0 and later · before 3.2.0.453affected
- 3.2.1 and later · before 3.2.1.73affected
- 4.0.0 and later · before 4.0.0.373affected
- 4.1.0 and later · before 4.1.0.236affected
- 4.2.0 and later · before 4.2.0.176affected
- 4.3.0 and later · before 4.3.0.88affected
- 4.4.0 and later · before 4.4.0.52affected
- 4.5.0 and later · before 4.5.0.35affected
WSO2 WSO2 Identity Server
- before 5.10.0unknown
- 5.10.0 and later · before 5.10.0.378affected
- 5.11.0 and later · before 5.11.0.425affected
- 6.0.0 and later · before 6.0.0.252affected
- 6.1.0 and later · before 6.1.0.253affected
- 7.0.0 and later · before 7.0.0.130affected
- 7.1.0 and later · before 7.1.0.38affected
- 7.2.0 and later · before 7.2.0.1affected
WSO2 WSO2 Identity Server as Key Manager
- before 5.10.0unknown
- 5.10.0 and later · before 5.10.0.369affected
WSO2 WSO2 Open Banking AM
- before 2.0.0unknown
- 2.0.0 and later · before 2.0.0.398affected
WSO2 WSO2 Open Banking IAM
- before 2.0.0unknown
- 2.0.0 and later · before 2.0.0.418affected
WSO2 WSO2 Traffic Manager
- 4.5.0 and later · before 4.5.0.34affected
- 4.6.0 and later · before 4.6.0.1affected
WSO2 WSO2 Universal Gateway
- 4.5.0 and later · before 4.5.0.34affected
- 4.6.0 and later · before 4.6.0.1affected

Same product

wso2: all records

Other highest-scoring records for the same primary product.

CVE-2026-5430Authentication Bypass via JWT Algorithm Mismatch in Multiple WSO2 Products Allows Account TakeoverKEV
77This week
CVE-2026-1728Privilege Escalation via System REST APIs in Multiple WSO2 Products Permits Admin Account Takeover
39Monitor
CVE-2025-9312Improper Certificate-Based Authentication Enforcement in Multiple WSO2 Products
39Monitor

Published before and after this one in the same product

← EarlierCVE-2025-15039Aug 6, 2026 · Account Takeover via Conditional Authentication Script Logic in Multiple WSO2 Products
37Monitor
← EarlierCVE-2026-0637Aug 6, 2026 · Header Injection via Custom URL Configuration in Multiple WSO2 Products Allows Open Redirect and Log Forgery
21Monitor
← EarlierCVE-2026-3416Sep 3, 2026 · Predictable Pseudorandom Number Generation via Webhook HMAC Secret Generation in Multiple WSO2 Products Allows Forged Event Payloads
30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

—

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

CVE-2026-543028 days apartAuthentication Bypass via JWT Algorithm Mismatch in Multiple WSO2 Products Allows Account TakeoverKEV
77This week

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Someone on the same network segment can trigger it.
Administrator privileges are required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Impact can extend beyond the vulnerable component (scope changes).

Attack vector: Adjacent
Attack complexity: Low
Privileges required: High
User interaction: None
Scope: Changed
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-78 · Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

CVSS vector

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

nvd-secondary

Root cause

User input is inserted as text into a shell command. The shell may interpret special characters in the input as part of the command.

The bug in code

The whole CWE-78 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const host = req.body.host;
2exec("ping -c 1 " + host, onResult);

Fixed

1const host = req.body.host;
2if (!/^[a-z0-9.-]{1,253}$/i.test(host)) return res.sendStatus(400);
3execFile("ping", ["-c", "1", host], onResult);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4771/

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records