dbcve.org
ViewpowerApplication · Voltronicpower

CVE-2023-51588

HIGH · 7.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 →
80/100
Remediation priority · High
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 MySQL Use of Hard-coded Credentials Local Privilege Escalation Vulnerability. This vulnerability allows local attackers to escalate privileges on affected installations of Voltronic Power ViewPower Pro. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability. The specific flaw exists within the configuration of a MySQL instance. The issue results from hardcoded database credentials. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code in the context of SYSTEM. Was ZDI-CAN-22075.

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

ViewPower Pro stores hardcoded MySQL credentials in its database configuration. An attacker with the ability to execute low-privileged code on the target system can exploit these credentials to access the MySQL database and escalate privileges to SYSTEM, achieving arbitrary code execution.

MitigationReplace hardcoded MySQL credentials with strong, unique credentials stored securely; apply vendor patches when available; restrict local access to the system to limit initial attack vectors.

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

CVSS:3.0/AV:L/AC:L/PR:L/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. Identify if ViewPower software is installed
    Check system for installed software named ViewPower, Voltronicpower Viewpower, or related service. Look in Program Files, Program Files (x86), or use system inventory tools.
    Affected if ViewPower Pro or Voltronicpower Viewpower is installed on the system
  2. Determine installed version of ViewPower
    Locate the ViewPower installation directory and check version information in executable metadata, about dialog, or version file. Common tools: right-click executable > Properties > Details, or check README/version.txt files in install folder.
    Affected if Installed version equals exactly 2.0-22165
  3. Locate MySQL database configuration file
    Search the ViewPower installation directory for configuration files (commonly .ini, .conf, .xml, .config, or database-specific files) that contain MySQL connection settings.
    Affected if A MySQL configuration file exists within the ViewPower installation directory
  4. Inspect database configuration for hardcoded credentials
    Open the MySQL configuration file and examine connection string or credential fields. Look for username and password values stored directly in the configuration, not retrieved from external secure storage.
    Affected if Hardcoded username and password values are present in the MySQL configuration (credentials stored in plaintext within the config file)

System is affected if ViewPower version 2.0-22165 is installed AND hardcoded MySQL credentials are found in the database configuration file, allowing any user with local code execution to access the database and escalate to SYSTEM.

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

Replace hardcoded MySQL credentials with strong, unique credentials stored securely; apply vendor patches when available; restrict local access to the system to limit initial attack vectors.

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

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 locally
dbcve dependency scanner

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