dbcve.org
ViewpowerApplication · Voltronicpower

CVE-2023-51586

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 selectEventConfig SQL Injection 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 selectEventConfig method. The issue results from the lack of proper validation of a user-supplied string before using it to construct SQL queries. An attacker can leverage this vulnerability to execute code in the context of LOCAL SERVICE. Was ZDI-CAN-22072.

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 a critical SQL injection vulnerability in Voltronic Power ViewPower Pro's selectEventConfig method. The application fails to properly validate user-supplied input before incorporating it into SQL queries, allowing unauthenticated remote attackers to inject malicious SQL commands. This can be leveraged to achieve remote code execution in the context of the LOCAL SERVICE account.

MitigationRestrict network exposure of ViewPower Pro to only trusted users and monitor for indicators of compromise. Since no patch reference exists in this advisory, contact the vendor for available updates or consider compensating controls such as network segmentation and WAF rules.

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. Confirm ViewPower Pro installation and version
    Locate the ViewPower Pro installation directory and check for version information files, typically found in the application root or in an 'about' or 'version' file. Compare the installed version number to 2.0-22165.
    Affected if The installed version is exactly 2.0-22165.
  2. Identify the selectEventConfig endpoint
    Examine the application's web configuration files or HTTP request logs for the selectEventConfig method. This is typically exposed as a web service endpoint or API method that handles event configuration queries.
    Affected if The selectEventConfig method is present and accessible in the application.
  3. Check network exposure of ViewPower Pro service
    Review firewall rules, network ACLs, and service binding configurations to determine if the ViewPower Pro web interface is accessible from untrusted networks. Check listening ports (typically HTTP/HTTPS on common web ports).
    Affected if The ViewPower Pro service is exposed to untrusted or public networks without proper network segmentation.
  4. Review SQL query handling in application logs
    Examine ViewPower Pro application logs for any SQL syntax errors, unusual database queries, or indicators of SQL injection attempts, particularly those targeting event configuration functionality.
    Affected if SQL injection attempts or anomalous SQL queries are found in the logs.

A user is affected if they are running exactly version 2.0-22165 of ViewPower Pro with the selectEventConfig method exposed to untrusted networks.

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 exposure of ViewPower Pro to only trusted users and monitor for indicators of compromise. Since no patch reference exists in this advisory, contact the vendor for available updates or consider compensating controls such as network segmentation and WAF rules.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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