Unrestricted File UploadWeakness · CWE-434

CVE-2025-23171

HIGH · 7.2 CVSS v3.1 Published 2025-06-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
The Versa Director SD-WAN orchestration platform provides an option to upload various types of files. The Versa Director does not correctly limit file upload permissions. The UI appears not to allow file uploads but uploads still succeed. In addition, the Versa Director discloses the full filename of uploaded temporary files, including the UUID prefix. Insecure UCPE image upload in Versa Director allows an authenticated attacker to upload a webshell. Exploitation Status: Versa Networks is not aware of any reported instance where this vulnerability was exploited. Proof of concept for this vulnerability has been disclosed by third party security researchers. Workarounds or Mitigation: There are no workarounds to disable the GUI option. Versa recommends that Director be upgraded to one of the remediated software versions.

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 confidence

Versa Director SD-WAN orchestration platform contains an insecure file upload vulnerability in the UCPE image upload functionality. Despite the UI appearing to block file uploads, the backend does not properly enforce upload restrictions, allowing authenticated attackers to upload arbitrary files including webshells. Additionally, the platform discloses full filenames with UUID prefixes of temporary files, potentially aiding attackers in path traversal or further exploitation.

MitigationUpgrade Versa Director to a remediated software version as specified by Versa Networks; there are no workarounds to disable the vulnerable GUI option.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Versa Director is installed
    Check for Versa Director processes or services running on the system. Look for processes named 'versa' or services listening on typical Versa Director ports (port 443, 8443 typical for web UI).
    Affected if Versa Director software is running on the system
  2. Identify UCPE image upload functionality
    Access the Versa Director web GUI and navigate to the UCPE (Unified Customer Premises Equipment) image upload section. Typically found under Services, Templates, or similar sections dealing with SD-WAN appliance images.
    Affected if The UCPE image upload feature is present and accessible in the GUI
  3. Check authentication requirements for upload endpoint
    Attempt to access the file upload functionality. Determine if the endpoint requires authentication by observing whether login is enforced before upload options become available.
    Affected if The upload endpoint is accessible to authenticated users without additional access control restrictions
  4. Verify backend enforces file type restrictions
    Test the upload endpoint by sending a request with a non-image file extension (e.g., .jsp, .php, .sh) to the UCPE upload API endpoint. Observe whether the backend accepts or rejects the file based on content-type or extension.
    Affected if The backend accepts files with extensions not matching expected image types (e.g., .iso, .img) or allows executable file types
  5. Check for temporary file disclosure
    After triggering an upload attempt, examine server responses or logs for references to temporary files with UUID prefixes. Look for paths that reveal the full filename structure.
    Affected if The system returns or logs filenames containing UUID prefixes for temporary upload files, exposing the full path structure

If Versa Director is running with the UCPE image upload feature accessible to authenticated users and the backend accepts arbitrary file types (not restricted to legitimate image formats), the environment is likely affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Versa Director to a remediated software version as specified by Versa Networks; there are no workarounds to disable the vulnerable GUI option.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-23171 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-23171 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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