dbcve.org
Enterprise IntegratorApplication · Wso2

CVE-2025-1862

HIGH · 7.2 CVSS v3.1 Published 2025-09-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
An arbitrary file upload vulnerability exists in multiple WSO2 products due to improper validation of user-supplied filenames in the BPEL uploader SOAP service endpoint. A malicious actor with administrative privileges can upload arbitrary files to a user-controlled location on the server. By leveraging this vulnerability, an attacker can upload a specially crafted payload and achieve remote code execution (RCE), potentially compromising the server and its data.

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 confidence

This is an arbitrary file upload vulnerability in the BPEL uploader SOAP service endpoint of multiple WSO2 products. The issue stems from improper validation of user-supplied filenames, allowing authenticated administrators to upload files to arbitrary locations on the server. This can be leveraged to achieve remote code execution.

MitigationImplement strict filename validation and path sanitization in the BPEL uploader SOAP endpoint to prevent path traversal and ensure uploaded files are restricted to designated safe directories. Additionally, apply vendor-provided patches for affected WSO2 products.

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
Enterprise IntegratorApplication
Affected:= 6.6.0
Identity ServerApplication
Affected:= 5.10.0= 5.11.0= 6.0.0= 6.1.0
Identity Server As Key ManagerApplication
Affected:= 5.10.0
Open Banking IamApplication
Affected:= 2.0.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify your WSO2 product and version
    Locate the version file in your WSO2 installation (typically in the product's root directory or carbon.xml). Common locations: <install>/bin/wso2server.sh --version or check <install>/repository/conf/etc/carbon.xml for the version element.
    Affected if The product is WSO2 Enterprise Integrator 6.6.0, WSO2 Identity Server 5.10.0/5.11.0/6.0.0/6.1.0, WSO2 Identity Server As Key Manager 5.10.0, or WSO2 Open Banking Iam 2.0.0
  2. Locate the BPEL uploader SOAP endpoint
    Check if the BPEL uploader service is deployed by searching for 'BPELUploader' in the <install>/repository/deployment/server/synapse-configs/default/services/ directory, or by examining the WSDL at /services/BPELUploader?wsdl if the endpoint is accessible.
    Affected if The BPELUploader service WSDL is accessible and the service .aar file exists in the deployment directory
  3. Verify administrator access to the endpoint
    Confirm that administrator credentials can be used to authenticate against the /services/BPELUploader SOAP endpoint. Check the repository/conf/identity/identity.xml for admin service exposure settings.
    Affected if The BPEL uploader endpoint accepts authenticated administrator requests without additional restrictions
  4. Inspect upload directory configuration
    Examine the BPEL uploader service configuration file (BPELUploader.aar) or the related deployment descriptors to determine the allowed upload path. Look for path traversal vulnerability indicators in the file upload handling code.
    Affected if The service lacks proper filename validation and allows path traversal patterns in the upload request

You are affected if you run any of the listed WSO2 product versions AND the BPEL uploader SOAP service endpoint is deployed and accessible to authenticated administrators.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict filename validation and path sanitization in the BPEL uploader SOAP endpoint to prevent path traversal and ensure uploaded files are restricted to designated safe directories. Additionally, apply vendor-provided patches for affected WSO2 products.

Fix this in Enterprise Integrator Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1862 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-1862 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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