CVE-2025-5717
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 authenticated remote code execution (RCE) vulnerability exists in multiple WSO2 products due to improper input validation in the event processor admin service. A user with administrative access to the SOAP admin services can exploit this flaw by deploying a Siddhi execution plan containing malicious Java code, resulting in arbitrary code execution on the server. Exploitation of this vulnerability requires a valid user account with administrative privileges, limiting the attack surface to authenticated but potentially malicious users.
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 confidenceImproper input validation in the WSO2 event processor admin service allows authenticated administrators to deploy Siddhi execution plans containing malicious Java code, resulting in arbitrary code execution on the server.
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= 3.0.0= 3.1.0= 3.2.0= 3.2.1= 4.0.0= 4.1.0= 4.2.0= 4.3.0= 4.4.0= 4.5.0= 2.0.0= 4.5.0CVSS 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 WSO2 product and versionLocate the product version from the product banner, release_info.xml file, or the management console about page. Common locations include <product-home>/bin/wso2server.sh --version or the Carbon console at /carbon/admin/about.jspAffected if The installed version matches any of these: API Control Plane 4.5.0; API Manager 3.0.0, 3.1.0, 3.2.0, 3.2.1, 4.0.0, 4.1.0, 4.2.0, 4.3.0, 4.4.0, 4.5.0; Open Banking AM 2.0.0; Traffic Manager 4.5.0
-
Confirm event processor admin service is accessibleCheck if the EventProcessorAdminService endpoint is reachable. This is typically at /services/EventProcessorAdminService. Attempt a curl or HTTP request to this endpoint with proper authentication credentials.Affected if The admin service responds successfully and accepts authenticated requests, indicating it is enabled and exposed
-
Verify Siddhi execution plan deployment capabilityReview the management console or check for Siddhi-related deployment endpoints. Look for the ability to create or deploy new Siddhi applications through the Event Processor UI or admin APIs.Affected if The Siddhi execution plan deployment feature is available and operational in the environment
-
Review admin audit logs for suspicious execution plan activityExamine WSO2 Carbon logs and admin audit logs for events related to EventProcessorAdminService, specifically CreateSiddhiApp or deploySiddhiApp operations. Look for unexpected or unauthorized deployment events.Affected if Logs show deployment of Siddhi execution plans that were not initiated by trusted administrators or contain unexpected Java code constructs
A user is affected if they run any of the listed product versions AND the event processor admin service is accessible to authenticated administrators with the ability to deploy Siddhi execution plans.
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.
From vendor dataRestrict admin service access to trusted users only, implement strict input validation on Siddhi execution plan deployments, apply vendor patches when available, and consider network segmentation to limit exposure.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5717 — 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-5717 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