CVE-2025-11093
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceArbitrary code execution vulnerability in WSO2 Micro Integrator, Enterprise Integrator, and API Manager due to insufficient access controls on GraalJS and NashornJS Script Mediator engines. Authenticated privileged users (administrators in MI/EI, administrators and API creators in API Manager) can execute arbitrary code within the integration runtime environment.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 4.5.0, < 4.5.0.29>= 3.1.0, < 3.1.0.345>= 3.2.0, < 3.2.0.446>= 3.2.1, < 3.2.1.66>= 4.1.0, < 4.1.0.228>= 4.2.0, < 4.2.0.169>= 4.3.0, < 4.3.0.81>= 4.4.0, < 4.4.0.45>= 4.5.0, < 4.5.0.28>= 6.6.0, < 6.6.0.224>= 4.0.0, < 4.0.0.145>= 4.1.0, < 4.1.0.147>= 4.2.0, < 4.2.0.141>= 4.3.0, < 4.3.0.42>= 4.4.0, < 4.4.0.27>= 4.5.0, < 4.5.0.27>= 4.5.0, < 4.5.0.27CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed WSO2 product and versionLocate the product version in the product-specific configuration file or startup logs. For WSO2 API Manager, check the version in the product header or management console. For Micro Integrator and Enterprise Integrator, check the version file or startup banner.Affected if The installed version falls within any of the affected version ranges listed for the CVE.
-
Verify the Script Mediator feature is availableCheck whether the GraalJS or NashornJS Script Mediator is enabled or installed in the integration environment. This may be visible in the management console under mediators or in the product feature configuration.Affected if The Script Mediator engine (GraalJS or NashornJS) is present and active in the environment.
-
Review user role assignments for Script Mediator accessExamine the roles assigned to users who have access to the Script Mediator functionality. In the WSO2 identity or management console, inspect which roles permit use of the Script Mediator.Affected if Non-administrative users (such as API creators) or untrusted administrators have Script Mediator access.
-
Check for custom script execution configurationsInspect any deployed scripts or configurations that use the Script Mediator. Look for custom JavaScript or other scripts configured in mediation sequences or API definitions.Affected if Custom scripts are deployed that leverage the Script Mediator for code execution.
A user is affected if they run a WSO2 product version within the affected ranges AND have the Script Mediator enabled with permissions granted to users beyond trusted administrators.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.1.0.3453.2.0.4463.2.1.66
Restrict or disable the GraalJS and NashornJS Script Mediator engines for non-administrative users; implement allow-listing for approved scripts; review user role assignments to limit exposure.
Upgrade to the minimum fixed version for your specific product: Api Control Plane 4.5.0.29 | Api Manager 3.1.0.345/3.2.0.446/3.2.1.66/4.1.0.228 | Enterprise Integrator 6.6.0.224 | Micro Integrator 4.0.0.145/4.1.0.147/4.2.0.141/4.3.0.42 | Traffic Manager 4.5.0.27 | Universal Gateway 4.5.0.27
- Identify the specific WSO2 product from the affected list (Api Control Plane, Api Manager, Enterprise Integrator, Micro Integrator, Traffic Manager, or Universal Gateway)
- Determine the currently installed version using product documentation or administrative console
- For Api Control Plane: upgrade to version 4.5.0.29 or later
- For Api Manager: upgrade to version 3.1.0.345, 3.2.0.446, 3.2.1.66, or 4.1.0.228 or later (depending on your branch)
- For Enterprise Integrator: upgrade to version 6.6.0.224 or later
- For Micro Integrator: upgrade to version 4.0.0.145, 4.1.0.147, 4.2.0.141, or 4.3.0.42 or later (depending on your branch)
- For Traffic Manager: upgrade to version 4.5.0.27 or later
- For Universal Gateway: upgrade to version 4.5.0.27 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11093 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-11093 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data