Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 0.56% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2025
CVE-2025-10907High confidence
Authenticated Arbitrary File Upload in Multiple WSO2 Products via SOAP Admin Services Leading to Remote Code Execution
WSO2 · WSO2 API Manager
8.4HighCVSS 3.1
Within 7 days
Patch availableHigh technical severity; prioritise exposed affected systems while verifying vendor guidance.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:High, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict local access and enforce least privilege on affected hosts.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs WSO2 WSO2 API Manager and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
High technical severity; prioritise exposed affected systems while verifying vendor guidance.
Patch available01
What, why and how
An 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.
What
An 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.
Why
The upload path does not sufficiently restrict the type, name, location or later execution of attacker-supplied files.
How
An attacker operating through an adjacent network may attempt exploitation with elevated privileges. If successful, the issue may execute code or commands in the affected security context.
What
An 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.
Why
The upload path does not sufficiently restrict the type, name, location or later execution of attacker-supplied files.
How
An attacker operating through an adjacent network may attempt exploitation with elevated privileges. If successful, the issue may execute code or commands in the affected security context.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- an adjacent network → Unrestricted Upload of File with Dangerous Type → execute code or commands in the affected security context
- Attack surface
- Adjacent
- Privileges required
- High: elevated access is required
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Changed: exploitation can affect a different security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-434 ↗
CWE-434: Unrestricted Upload of File with Dangerous Type. The product allows the upload or transfer of dangerous file types that are automatically processed within its environment.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVAdjacentAttack vector: The attacker must be on an adjacent or logically close network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRHighPrivileges required: The attacker needs elevated or administrative privileges.UINoneUser interaction: No action by another user is required.SChangedScope: The attack can affect a component governed by a different security authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.- Post-exploitation / living off the land
- After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Patch available
- Affected
- WSO2 API Manager: < 3.1.0, 3.1.0 < 3.1.0.345, 3.2.0 < 3.2.0.448, 3.2.1 < 3.2.1.66, 4.0.0 < 4.0.0.367, 4.1.0 < 4.1.0.230, 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
- WSO2 Open Banking IAM: < 2.0.0, 2.0.0 < 2.0.0.414
- WSO2 Open Banking AM: < 2.0.0, 2.0.0 < 2.0.0.394
- WSO2 API Control Plane: 4.5.0 < 4.5.0.29
- WSO2 Universal Gateway: 4.5.0 < 4.5.0.27
- WSO2 Traffic Manager: 4.5.0 < 4.5.0.27
- WSO2 Micro Integrator: < 4.0.0, 4.0.0 < 4.0.0.145, 4.1.0 < 4.1.0.147, 4.2.0 < 4.2.0.141
- WSO2 Identity Server: < 5.10.0, 5.10.0 < 5.10.0.375, 5.11.0 < 5.11.0.419, 6.0.0 < 6.0.0.248, 6.1.0 < 6.1.0.248, 7.0.0 < 7.0.0.124, 7.1.0 < 7.1.0.31
- WSO2 Identity Server as Key Manager: < 5.10.0, 5.10.0 < 5.10.0.365
- WSO2 Enterprise Integrator: < 6.6.0, 6.6.0 < 6.6.0.224
- org.jaggeryjs:org.jaggeryjs.jaggery.app.mgt: 0.14.13 < 0.14.13.8, 0.14.16 < 0.14.16.1
- org.wso2.carbon.event-processing:org.wso2.carbon.event.simulator.core: 2.2.14 < 2.2.14.7, 2.2.17 < 2.2.17.2, 2.3.1 < 2.3.1.3
- org.wso2.carbon.mediation:org.wso2.carbon.mediation.library: 4.7.30 < 4.7.30.47, 4.7.61 < 4.7.61.62, 4.7.99 < 4.7.99.304, 4.7.131 < 4.7.131.22, 4.7.175 < 4.7.175.30, 4.7.188 < 4.7.188.12, 4.7.204 < 4.7.204.13, 4.7.221 < 4.7.221.7, 4.7.245 < 4.7.245.7
- org.wso2.carbon.deployment:org.wso2.carbon.module.mgt: 4.9.15 < 4.9.15.2, 4.10.1 < 4.10.1.1, 4.10.9 < 4.10.9.2, 4.11.1 < 4.11.1.3, 4.11.3 < 4.11.3.3, 4.11.7 < 4.11.7.5, 4.11.14 < 4.11.14.2, 4.11.17 < 4.11.17.3, 4.11.18 < 4.11.18.1
- org.wso2.carbon.deployment:org.wso2.carbon.webapp.mgt: 4.10.1 < 4.10.1.1, 4.10.9 < 4.10.9.2, 4.11.1 < 4.11.1.3, 4.11.3 < 4.11.3.3, 4.11.7 < 4.11.7.5, 4.11.14 < 4.11.14.2, 4.11.17 < 4.11.17.3, 4.11.18 < 4.11.18.1
- org.apache.ws.commons.axiom.wso2:axiom: 1.2.11 < 1.2.11.wso2v17_5
- org.wso2.carbon:org.wso2.carbon.base: 4.5.3 < 4.5.3.46, 4.6.0 < 4.6.0.2005, 4.6.1 < 4.6.1.153, 4.6.2 < 4.6.2.668, 4.6.3 < 4.6.3.37, 4.6.4 < 4.6.4.15, 4.7.1 < 4.7.1.72, 4.8.1 < 4.8.1.40, 4.9.0 < 4.9.0.103, 4.9.26 < 4.9.26.26, 4.9.27 < 4.9.27.11, 4.9.28 < 4.9.28.12, 4.10.9 < 4.10.9.71, 4.10.42 < 4.10.42.14
- org.wso2.carbon:org.wso2.carbon.utils: 4.5.3 < 4.5.3.46, 4.6.0 < 4.6.0.2005, 4.6.1 < 4.6.1.153, 4.6.2 < 4.6.2.668, 4.6.3 < 4.6.3.37, 4.6.4 < 4.6.4.15, 4.7.1 < 4.7.1.72, 4.8.1 < 4.8.1.40, 4.9.0 < 4.9.0.103, 4.9.26 < 4.9.26.26, 4.9.27 < 4.9.27.11, 4.9.28 < 4.9.28.12, 4.10.9 < 4.10.9.71, 4.10.42 < 4.10.42.14
- Fixed
- org.wso2.carbon.event-processing:org.wso2.carbon.event.simulator.core: 2.3.19 ≤ *
- org.wso2.carbon.mediation:org.wso2.carbon.mediation.library: 4.7.262 ≤ *
- org.wso2.carbon.deployment:org.wso2.carbon.module.mgt: 4.11.24 ≤ *
- org.wso2.carbon.deployment:org.wso2.carbon.webapp.mgt: 4.11.24 ≤ *
- org.apache.ws.commons.axiom.wso2:axiom: 1.2.11-wso2v21 ≤ *
- org.wso2.carbon:org.wso2.carbon.base: 4.9.30 ≤ 4.9.*, 4.10.95 ≤ *
- org.wso2.carbon:org.wso2.carbon.utils: 4.9.30 ≤ 4.9.*, 4.10.95 ≤ *
- Action
- Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
- Workaround
- No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04
Evidence and provenance
Published 5 Nov 2025 · Last source change 5 Nov 2025, 18:49 UTC · CWE-434 · Unrestricted Upload of File with Dangerous Type
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2025-37942
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.