dbcve.org
ViewpowerApplication · Voltronicpower

CVE-2023-51583

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 UpsScheduler Exposed Dangerous Method Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Voltronic Power ViewPower. Authentication is not required to exploit this vulnerability. The specific flaw exists within the UpsScheduler class. The issue results from an exposed dangerous method. An attacker can leverage this vulnerability to execute code in the context of SYSTEM. Was ZDI-CAN-22036.

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

The vulnerability exists in the UpsScheduler class of Voltronic Power ViewPower UPS management software. An exposed dangerous method within this class can be invoked by remote attackers without authentication, allowing execution of arbitrary code in SYSTEM context.

MitigationRestrict network access to ViewPower services from untrusted networks. Monitor for unauthorized access attempts and apply vendor patches when available.

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:= 1.04.21353

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. Confirm ViewPower installation
    Check for ViewPower installation by looking for the application in Windows Programs and Features, or search for ViewPower in Program Files directory (typically C:\Program Files\Voltronic Power\ViewPower or C:\Program Files (x86)\Voltronic Power\ViewPower)
    Affected if ViewPower software is found installed on the system
  2. Identify installed ViewPower version
    Locate the ViewPower executable (ViewPower.exe or similar) and check its file version properties. Right-click the executable, select Properties, and view the Details tab for the Version information. Alternatively, check the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ for ViewPower entry and its DisplayVersion value
    Affected if Installed version matches 1.04.21353 exactly
  3. Verify UpsScheduler service exists and is running
    Open Windows Services (services.msc) and look for a service related to UpsScheduler or ViewPower Scheduler. Check if the service status is Running. Alternatively, run 'sc query' command to enumerate services containing 'ups' or 'scheduler' in the name
    Affected if UpsScheduler or related ViewPower scheduler service is installed and running
  4. Check for exposed network listeners
    Use netstat command (netstat -an | findstr LISTENING) or PowerShell (Get-NetTCPConnection -State Listen) to identify ports on which the ViewPower service is listening. Common ports for ViewPower include 8080, 8888, or 9999. Also check Windows Firewall rules for any inbound rules allowing traffic to ViewPower executables
    Affected if ViewPower service is listening on any network-accessible port and accepts remote connections

System is affected if ViewPower version 1.04.21353 is installed with the UpsScheduler service running and exposed to network access, allowing unauthenticated remote code execution.

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

Restrict network access to ViewPower services from untrusted networks. Monitor for unauthorized access attempts and apply vendor patches when available.

Fix this in Viewpower Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-51583 — 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-51583 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