CVE-2025-10907
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 file upload vulnerability exists in multiple WSO2 products due to insufficient validation of uploaded content and destination in SOAP admin services. A malicious actor with administrative privileges can upload a specially crafted file to a user-controlled location within the deployment. Successful exploitation may lead to remote code execution (RCE) on the server, depending on how the uploaded file is processed. By default, this vulnerability is only exploitable by users with administrative access to the affected SOAP services.
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 confidenceWSO2 products contain an arbitrary file upload vulnerability in SOAP admin services due to insufficient validation of both uploaded file content and the destination path. An authenticated administrator can upload malicious files to user-controlled locations within the deployment, potentially achieving remote code execution depending on file processing.
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.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= 6.6.0= 5.10.0= 5.11.0= 6.0.0= 6.1.0= 7.0.0= 7.1.0= 5.10.0= 2.0.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 versionCheck the product version by locating the release.info or version.txt file in the installation directory, or by examining the product banner at the login page or administrative console.Affected if The installed product matches any of the affected versions listed in the CVE (API Manager 3.1.0-4.5.0, Identity Server 5.10.0-7.1.0, Enterprise Integrator 6.6.0, etc.)
-
Verify SOAP admin services are accessibleCheck if the SOAP admin services endpoint (typically at /services/) is exposed and reachable. Inspect the server configuration files (axis2.xml, carbon.xml) for enabled admin services.Affected if SOAP admin services are enabled and network-accessible without additional authentication controls beyond basic admin credentials.
-
Review administrative user accessExamine the user management configuration (user-mgt.xml) and audit logs to identify which accounts have administrator privileges and how they authenticate.Affected if Multiple administrator accounts exist or admin credentials are shared among multiple users, increasing the risk of credential misuse.
-
Inspect deployment directories for unauthorized filesSearch deployment directories (repository/deployment/server/webapp, repository/resources, or tmp folders) for unexpected .jsp, .war, .jar, or executable files with recent modification dates.Affected if Any suspicious files are found in deployment directories that were not intentionally placed there by administrators.
You are affected if you run any of the listed WSO2 product versions with SOAP admin services enabled and an authenticated administrator can upload files to arbitrary locations within the deployment.
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 · scopedApply vendor-supplied security patches for all affected WSO2 products. If patches are unavailable, implement strict validation of file uploads in SOAP services and restrict administrative access to minimize attack surface.
Upgrade to the fixed version or apply patch as specified in WSO2 security advisory for CVE-2025-1097 at security.docs.wso2.com
- 1. Identify the specific WSO2 product and version from the affected list (API Control Plane 4.5.0, API Manager 3.1.0/3.2.0/3.2.1/4.0.0, Enterprise Integrator 6.6.0, Identity Server 5.10.0/5.11.0/6.0.0/6.1.0, Identity Server as Key Manager 5.10.0, Open Banking AM 2.0.0, Open Banking IAM 2.0.0, Traffic Manager 4.5.0)
- 2. Access the WSO2 Security Advisories page at security.docs.wso2.com to locate CVE-2025-10907
- 3. Download and apply the security patch specified in the advisory for your product version
- 4. Alternatively, upgrade to the fixed version number indicated in the WSO2 security advisory for your product
- 5. After applying the patch or upgrade, restart the affected WSO2 services
- 6. Verify the fix by testing file upload functionality through the SOAP admin services
- 7. Confirm the upload destination is properly restricted to allowed directories only
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10907 — 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-10907 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