# CVE-2025-11093: Code injection in WSO2 API Control Plane

> Privileged users can execute arbitrary code via Script Mediator engines in WSO2 products, potentially compromising the integration runtime environment.

- **Severity:** High 8.4 (`CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Nov 2025
- **Updated:** 5 Nov 2025
- **Also known as:** GHSA-qfqc-4pqq-rfmh

## What is CVE-2025-11093?

CVE-2025-11093 is a high-severity code injection vulnerability in Wso2 Api Manager, published on 5 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2025-11093?

It affects 6 products.


Products: Wso2 Api Control Plane, Wso2 Api Manager, Wso2 Enterprise Integrator, Wso2 Micro Integrator, Wso2 Traffic Manager, Wso2 Universal Gateway.

## How do I fix CVE-2025-11093?

No fix has been published for CVE-2025-11093 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-11093 being exploited?

There is no known exploitation of CVE-2025-11093 in the wild and no public exploit code.

## Other vulnerabilities in Wso2 Api Manager

- [CVE-2026-5430](https://insights.sbomify.com/CVE-2026-5430/): WSO2 Multiple Products Path Traversal Vulnerability (critical 10.0, exploited in the wild)
- [CVE-2026-1728](https://insights.sbomify.com/CVE-2026-1728/): Privilege Escalation via System REST APIs in Multiple WSO2 Products Permits Admin Account Takeover (critical 9.8)
- [CVE-2025-9312](https://insights.sbomify.com/CVE-2025-9312/): Improper Certificate-Based Authentication Enforcement in Multiple WSO2 Products (critical 9.8)
- [CVE-2025-10611](https://insights.sbomify.com/CVE-2025-10611/): Potential Broken Access Control in Multiple WSO2 Products via System REST APIs (critical 9.8)
- [CVE-2025-9152](https://insights.sbomify.com/CVE-2025-9152/): Improper Privilege Management in Multiple WSO2 API Manager via keymanager-operations DCR Endpoint (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-11093 and fix it if it is affected.

What it is: CVE-2025-11093 is a high-severity code injection vulnerability in Wso2 Api Manager, published on 5 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-11093 in the wild and no public exploit code.

Affected product: Wso2 Api Manager. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-11093/ (Markdown: https://insights.sbomify.com/CVE-2025-11093/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-11093
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-11093
- OSV: https://osv.dev/vulnerability/CVE-2025-11093

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-11093/
Summaries are generated and may contain mistakes; the official description above is the record.