CVE-2025-3125VulnerabilityPublished 5 Nov 2025Updated 20 Jan 2026

CVE-2025-3125: WSO2 Identity Server · Unrestricted File Upload

Affects WSO2 Identity ServerSource CVE Database V5

Not known to be exploited · CVSS 6.7 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.7Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.9% chance of exploitation in 30 days – higher than 59% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Mavenorg.wso2.identity.server/wso2-identity-server`pkg:maven/org.wso2.identity.server/wso2-identity-server`Other threats	Affected =5.10.0 =5.11.0 =6.0.0 =6.1.0 =7.0.0 =7.1.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediately restrict administrative access to the CarbonAppUploader service endpoint to only trusted personnel and systems. 2. Implement strong multi-factor authentication (MFA) for all administrative accounts to reduce risk of credential compromise. 3. Monitor and audit all file upload activities and administrative actions within WSO2 Identity Server for suspicious behavior. 4. Apply principle of least privilege by limiting admin privileges to only those necessary for operational tasks. 5. Deploy network segmentation and firewall rules to isolate management interfaces from general network access. 6. Regularly update and patch WSO2 Identity Server to the latest versions once vendor patches become available. 7. Conduct internal penetration testing and vulnerability assessments focusing on admin interfaces and file upload functionalities. 8. Employ runtime application self-protection (RASP) or web application firewalls (WAF) with custom rules to detect and block malicious file uploads. 9. Educate administrators on phishing and credential security to prevent social engineering attacks that could lead to privilege escalation. 10. Maintain offline backups and incident response plans to quickly recover from potential compromises.

Description

An arbitrary file upload vulnerability exists in multiple WSO2 products due to improper input validation in the CarbonAppUploader admin service endpoint. An authenticated attacker with appropriate privileges can upload a malicious file to a user-controlled location on the server, potentially leading to remote code execution (RCE). This functionality is restricted by default to admin users; therefore, successful exploitation requires valid credentials with administrative permissions.

Impact

For European organizations, this vulnerability poses a significant risk especially for those relying on WSO2 Identity Server for critical identity and access management functions. Successful exploitation could lead to unauthorized remote code execution, enabling attackers to access sensitive data, manipulate authentication processes, or pivot within the network. This could result in data breaches, disruption of identity services, and potential compliance violations under GDPR due to unauthorized data access. The requirement for administrative credentials reduces the likelihood of external exploitation but increases the threat from insider attacks or credential theft. Organizations in sectors such as finance, healthcare, government, and telecommunications, which often deploy WSO2 Identity Server for secure authentication, are particularly vulnerable. The medium severity rating suggests that while the vulnerability is serious, it is not trivially exploitable without privileged access, but the impact on confidentiality and integrity is high.

CWE-434Unrestricted Upload of File with Dangerous Type (opens in a new tab)
Base weaknessLikelihood of exploit: MediumCWE Top 25 (2025): #12OWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product allows the upload or transfer of dangerous file types that are automatically processed within its environment.
Architecture and Design
Generate a new, unique filename for an uploaded file instead of using the user-supplied filename, so that no external input is used at all.
Architecture and Design · Enforcement by Conversion
When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
Architecture and Design
Consider storing the uploaded files outside of the web document root entirely. Then, use other mechanisms to deliver the files dynamically.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Web Service Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
File Upload (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V12.5.2 (opens in a new tab)
V13.1.5 (opens in a new tab)
V12.2.1 (opens in a new tab)
Attack patterns
Accessing Functionality Not Properly Constrained by ACLs (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

security.docs.wso2.com/en/latest/security-announcements/security-advisories/2025/WSO2-2025-3961/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 21 Jan 2026, 02:06 UTC

WeaknessesCWE-434

Technical details

References

Community reviews

Related threats