CVE-2025-13590
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 · uneditedA malicious actor with administrative privileges can upload an arbitrary file to a user-controlled location within the deployment via a system REST API. Successful uploads may lead to remote code execution. By leveraging the vulnerability, a malicious actor may perform Remote Code Execution by uploading a specially crafted payload.
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 confidenceThis is an authenticated arbitrary file upload vulnerability in a system REST API. An attacker with administrative privileges can bypass intended restrictions to upload files to arbitrary locations within the deployment filesystem, enabling remote code execution through specially crafted payloads.
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= 4.6.0= 4.2.0= 4.3.0= 4.4.0= 4.5.0= 4.6.0= 4.5.0= 4.6.0= 4.5.0= 4.6.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 the installed WSO2 product and versionLocate the product version file or check the management console about page. Common locations include <product-home>/bin/wso2server.bat or the admin console's 'About' section.Affected if The installed version matches any of the affected versions: API Control Plane 4.5.0 or 4.6.0; API Manager 4.2.0 through 4.6.0; Traffic Manager 4.5.0 or 4.6.0; Universal Gateway 4.5.0 or 4.6.0.
-
Verify the REST API is accessibleConfirm the WSO2 REST API endpoint is exposed. Check network configuration files or try accessing the API endpoint (typically at /api/ or /services/) from an authorized host.Affected if The REST API endpoint responds and accepts authenticated requests.
-
Confirm administrative user access existsDetermine if any user with administrative privileges exists in the system. Check the user store configuration or verify admin credentials are active in the identity provider.Affected if An administrative user account is present and able to authenticate to the system.
-
Locate the file upload endpointInspect the deployed API definitions or swagger/OpenAPI documentation to identify file upload endpoints within the REST API.Affected if A file upload endpoint exists and is reachable through the REST API.
-
Review upload directory configurationCheck the API Manager or gateway configuration files for the allowed upload directory paths. Look for any path validation or restriction settings on upload operations.Affected if The upload configuration allows writing files to arbitrary locations outside a restricted directory.
The environment is affected if it runs any of the listed WSO2 product versions AND has the REST API with administrative access and file upload functionality exposed.
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 dataImplement strict path validation to prevent directory traversal, restrict upload locations to a safe, non-executable directory, enforce allowlist-based file type validation, and ensure proper authorization checks are performed on all upload requests.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13590 — 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-13590 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