High Injection

CVE-2025-11093 — Arbitrary Code Execution with higher privileged users in Multiple WSO2 Products via Script Mediator Engines (GraalJS and NashornJS)

An arbitrary code execution vulnerability exists in multiple WSO2 products due to insufficient restrictions in the GraalJS and NashornJS Script Mediator engines. Authenticated users with elevated privileges can execute arbitrary code within the integration runtime environment. By default, access to these scripting engines is limited to administrators in WSO2 Micro Integrator and WSO2 Enterprise Integrator, while in WSO2 API Manager, access extends to both administrators and API creators. This may allow trusted-but-privileged users to perform unauthorized actions or compromise the execution environment.

Published Nov 5, 2025 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: WSO2

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.5% (30-day exploitation probability)+6
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.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.47%

ahead of 39% of scored CVEs · Oct 14, 2026

Affects

WSO2

Api Control Plane and 10 more

CVSS base

7.2

High · 3 source(s)

Prioritization reference: 8.4 provisional

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

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 Enterprise Integrator…).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
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	≥ 4.5.0 and < 4.5.0.29	Vulnerable	CVE Program (cve.org) e CISA ADP
WSO2	Api Control Plane	≥ 4.5.0 and < 4.5.0.29	Vulnerable	NIST National Vulnerability Database
WSO2	Api Manager	≥ 3.2.0 and < 3.2.0.446≥ 4.5.0 and < 4.5.0.28≥ 4.4.0 and < 4.4.0.45≥ 4.3.0 and < 4.3.0.81≥ 4.2.0 and < 4.2.0.169≥ 4.1.0 and < 4.1.0.228≥ 3.2.1 and < 3.2.1.66≥ 3.1.0 and < 3.1.0.345	Vulnerable	NIST National Vulnerability Database
WSO2	Api Manager	≥ 4.5.0 and < 4.5.0.28≥ 4.4.0 and < 4.4.0.45≥ 4.3.0 and < 4.3.0.81≥ 4.2.0 and < 4.2.0.169≥ 4.1.0 and < 4.1.0.228≥ 4.0.0 and < 4.0.0.366≥ 3.2.1 and < 3.2.1.66≥ 3.2.0 and < 3.2.0.446 and 1 more ≥ 3.1.0 and < 3.1.0.345	Vulnerable	CVE Program (cve.org) e CISA ADP
WSO2	Enterprise Integrator	≥ 6.6.0 and < 6.6.0.224	Vulnerable	NIST National Vulnerability Database
WSO2	Enterprise Integrator	≥ 6.6.0 and < 6.6.0.224	Vulnerable	CVE Program (cve.org) e CISA ADP
WSO2	Identity Server As Key Manager	≥ 5.10.0 and < 5.10.0.365	Vulnerable	CVE Program (cve.org) e CISA ADP
WSO2	Micro Integrator	≥ 4.2.0 and < 4.2.0.141≥ 4.3.0 and < 4.3.0.42≥ 4.4.0 and < 4.4.0.27≥ 4.0.0 and < 4.0.0.145≥ 4.1.0 and < 4.1.0.147	Vulnerable	NIST National Vulnerability Database
WSO2	Micro Integrator	≥ 4.0.0 and < 4.0.0.145≥ 4.1.0 and < 4.1.0.147≥ 4.2.0 and < 4.2.0.141≥ 4.3.0 and < 4.3.0.42≥ 4.4.0 and < 4.4.0.27	Vulnerable	CVE Program (cve.org) e CISA ADP
WSO2	Open Banking Am	≥ 2.0.0 and < 2.0.0.394	Vulnerable	CVE Program (cve.org) e CISA ADP
WSO2	Open Banking Iam	≥ 2.0.0 and < 2.0.0.414	Vulnerable	CVE Program (cve.org) e CISA ADP
WSO2	Org.apache.synapse:synapse-core	≥ 4.0.0.wso2v215 and < 4.0.0.wso2v215_26≥ 4.0.0.wso2v131 and < 4.0.0.wso2v131_5≥ 4.0.0.wso2v105 and < 4.0.0.wso2v105_13≥ 4.0.0.wso2v218 and < 4.0.0.wso2v218_1≥ 4.0.0.wso2v20 and < 4.0.0.wso2v20_93≥ 4.0.0.wso2v119 and < 4.0.0.wso2v119_27≥ 2.1.7.wso2v183 and < 2.1.7.wso2v183_72≥ 2.1.7.wso2v143 and < 2.1.7.wso2v143_121 and 3 more ≥ 2.1.7.wso2v271 and < 2.1.7.wso2v271_88≥ 2.1.7.wso2v227 and < 2.1.7.wso2v227_99≥ 2.1.7.wso2v319 and < 2.1.7.wso2v319_13	Vulnerable	CVE Program (cve.org) e CISA ADP
WSO2	Org.apache.synapse:synapse-extensions	≥ 4.0.0.wso2v131 and < 4.0.0.wso2v131_5≥ 4.0.0.wso2v105 and < 4.0.0.wso2v105_13≥ 4.0.0.wso2v218 and < 4.0.0.wso2v218_1≥ 4.0.0.wso2v215 and < 4.0.0.wso2v215_26≥ 4.0.0.wso2v20 and < 4.0.0.wso2v20_93≥ 4.0.0.wso2v119 and < 4.0.0.wso2v119_27≥ 2.1.7.wso2v183 and < 2.1.7.wso2v183_72≥ 2.1.7.wso2v319 and < 2.1.7.wso2v319_13 and 3 more ≥ 2.1.7.wso2v143 and < 2.1.7.wso2v143_121≥ 2.1.7.wso2v271 and < 2.1.7.wso2v271_88≥ 2.1.7.wso2v227 and < 2.1.7.wso2v227_99	Vulnerable	CVE Program (cve.org) e CISA ADP
WSO2	Traffic Manager	≥ 4.5.0 and < 4.5.0.27	Vulnerable	CVE Program (cve.org) e CISA ADP
WSO2	Traffic Manager	≥ 4.5.0 and < 4.5.0.27	Vulnerable	NIST National Vulnerability Database
WSO2	Universal Gateway	≥ 4.5.0 and < 4.5.0.27	Vulnerable	CVE Program (cve.org) e CISA ADP
WSO2	Universal Gateway	≥ 4.5.0 and < 4.5.0.27	Vulnerable	NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Privileges required

High

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

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
8.4	CVSS 3.1	High	—	—	WSO2 via CVE Program (cve.org) e CISA ADP
7.2	CVSS 3.1	High	1.2	5.9	nvd@nist.gov via NIST National Vulnerability Database

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)

Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 8.4 (ed10eef1-636d-4fbe-9993-6890dfa878f8 via NIST National Vulnerability Database) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-94 · Code Injection

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.47%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Look for parameters with command/query metacharacters and unexpected child processes of the service.

web/proxy/WAF logsnetwork IDS/IPSapplication logsendpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

2026
Affected products added · wso2/wso2 micro integrator, wso2/wso2 api manager, wso2/wso2 enterprise integrator, wso2/wso2 universal gateway, wso2/ws
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 13, 2026
CVSS changed · 7.2
Oct 13, 2026 · NIST National Vulnerability Database
Source status changed · → Analyzed
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
2025
CVE published
Nov 5, 2025 · WSO2

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

1 on the record

security.docs.wso2.com/en/latest/security-announcements/security-advisories/2025/WSO2-2025-4
Vendor Advisory, vendor-advisory, NIST National Vulnerability Database

Elsewhere on this site

WSO2
every CVE for this vendor

Injection
same class

CWE-94
other pages naming this weakness

Related CVEs (same products)

High CVE-2025-12737 OS Command Injection in WSO2 Api Control Plane Sep 3, 2026
High CVE-2026-3416 Use of Insufficiently Random Values in WSO2 Api Control Plane Sep 3, 2026
Critical CVE-2026-5430 WSO2 Multiple Products Path Traversal Vulnerability KEV Aug 6, 2026
Critical CVE-2026-1728 Improper Privilege Management in WSO2 Api Control Plane Aug 6, 2026
Medium CVE-2026-0637 Insertion of Sensitive Information into Log File in WSO2 Api Control Plane Aug 6, 2026
Critical CVE-2025-15039 The Conditional Authentication (Adaptive Authentication) script does not correctly… 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 fixed version, patch or mitigation documented.
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-11093 is "Arbitrary Code Execution with higher privileged users in Multiple WSO2 Products via Script Mediator Engines (GraalJS and NashornJS)", 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 7.2 describes technical severity. EPSS 0.47% estimates the probability of exploitation in 30 days; neither replaces your asset context. 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.