CVE-2025-3125
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 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.
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 confidenceArbitrary file upload vulnerability in the CarbonAppUploader admin service endpoint of multiple WSO2 products allows authenticated administrators to upload malicious files to user-controlled server locations due to improper input validation, potentially enabling remote code execution.
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.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= 5.10.0= 2.0.0= 4.5.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 your WSO2 product and versionLocate the product version in the product documentation, startup logs, or management console. For WSO2 API Manager check the management console under About > Version. For Identity Server check the dashboard. For Enterprise Integrator check the management console.Affected if The installed product and version matches any of the listed affected versions (API Manager 3.2.0-4.5.0, Identity Server 5.10.0-7.0.0, Enterprise Integrator 6.6.0, API Control Plane 4.5.0, Traffic Manager 4.5.0, Universal Gateway 4.5.0, Identity Server as Key Manager 5.10.0, Open Banking IAM 2.0.0)
-
Verify CarbonAppUploader endpoint accessibilityCheck if the CarbonAppUploader admin service endpoint is exposed. This is typically found at /services/CarbonAppUploader in the WSO2 management console or via SOAP requests to the admin services.Affected if The CarbonAppUploader endpoint is accessible without additional network restrictions or authentication barriers beyond standard admin credentials
-
Confirm administrator access to the environmentReview administrator account access and privileges in the WSO2 management console under Users and Roles or Identity Provider settings. Determine if multiple admin accounts exist and whether admin access is restricted.Affected if Authenticated administrator credentials exist and the CarbonAppUploader endpoint accepts admin authentication for file upload operations
-
Inspect server logs for CarbonAppUploader activityReview WSO2 server logs (typically in the logs directory) for any CarbonAppUploader invocations. Search for patterns containing 'CarbonAppUploader' and file upload operations, noting source IP addresses and uploaded file paths.Affected if Logs show CarbonAppUploader file upload operations to paths outside the expected application deployment directories, or to locations controllable by non-deployment users
-
Check for unexpected files in writable directoriesExamine user-writable directories on the server, particularly the uploads directory, temp directories, and the repository/deployment directory for unfamiliar script files (jsp, asp, php) or executable artifacts that were not intentionally deployed.Affected if Unexpected executable files appear in directories that should not contain uploaded content, especially with timestamps corresponding to administrator sessions
You are affected if you are running any of the listed WSO2 product versions AND the CarbonAppUploader endpoint is accessible to authenticated administrators who can upload files to arbitrary server locations.
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 and validate administrative access to the CarbonAppUploader endpoint, implement strict input validation for file upload paths and content, and apply vendor-provided patches for affected WSO2 products.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3125 — 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-3125 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