dbcve.org
ViewpowerApplication · Voltronicpower

CVE-2023-51590

CRITICAL · 9.8 CVSS v3.0 Published 2024-05-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Voltronic Power ViewPower Pro UpLoadAction Unrestricted File Upload Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Voltronic Power ViewPower Pro. Authentication is not required to exploit this vulnerability. The specific flaw exists within the UpLoadAction class. The issue results from the lack of proper validation of user-supplied data, which can allow the upload of arbitrary files. An attacker can leverage this vulnerability to execute code in the context of LOCAL SERVICE. Was ZDI-CAN-22080.

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

This is an unauthenticated unrestricted file upload vulnerability in the UpLoadAction class of Voltronic Power ViewPower Pro. The application fails to validate user-supplied data during file upload operations, allowing attackers to upload arbitrary files (including executable content) to the server. Successful exploitation enables remote code execution in the context of the LOCAL SERVICE account.

MitigationImplement strict server-side validation of uploaded files including magic byte verification, extension allow-listing, and content-type validation; store uploads outside web root; disable script execution in upload directories.

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
ViewpowerApplication
Affected:= 2.0-22165

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/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. Locate ViewPower Pro installation
    Check common installation directories such as C:\Program Files\ViewPower Pro, C:\Program Files (x86)\ViewPower Pro, or the installation path specified during setup. Also check services.msc for a service named 'ViewPower' or similar.
    Affected if ViewPower Pro is installed on the system
  2. Determine installed version
    Open the application or check version information in the Windows installer, about dialog, or version file within the installation directory. Look for version string '2.0-22165'.
    Affected if The installed version is exactly 2.0-22165
  3. Identify web interface exposure
    Check if the ViewPower Pro web server is running (typically on port 8080, 8081, or 8090). Access the base URL and look for the upload functionality or UpLoadAction endpoint.
    Affected if The web interface is accessible and the UpLoadAction upload endpoint is exposed
  4. Verify upload functionality exists
    If accessible, examine the web application's available actions and parameters, specifically looking for UpLoadAction or any file upload mechanism that accepts user-supplied file data without authentication.
    Affected if The UpLoadAction class and unauthenticated file upload functionality is present and accessible

If ViewPower Pro version 2.0-22165 is installed with its web interface and UpLoadAction endpoint exposed, the environment is vulnerable to unauthenticated arbitrary file upload.

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

Implement strict server-side validation of uploaded files including magic byte verification, extension allow-listing, and content-type validation; store uploads outside web root; disable script execution in upload directories.

Fix this in Viewpower Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-51590 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2023-51590 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