dbcve.org
ViewpowerApplication · Voltronicpower

CVE-2023-51591

HIGH · 7.5 CVSS v3.1 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 →
84/100
Remediation priority · High
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 doDocument XML External Entity Processing Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information on affected installations of Voltronic Power ViewPower Pro. Authentication is not required to exploit this vulnerability. The specific flaw exists within the doDocument method. Due to the improper restriction of XML External Entity (XXE) references, a crafted document specifying a URI causes the XML parser to access the URI and embed the contents back into the XML document for further processing. An attacker can leverage this vulnerability to disclose information in the context of LOCAL SERVICE. Was ZDI-CAN-22081.

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 XXE (XML External Entity) vulnerability in Voltronic Power ViewPower Pro's doDocument method. The XML parser does not properly restrict external entity references, allowing an unauthenticated remote attacker to craft XML documents containing URIs that point to internal resources (file:// URLs, etc.). The parser accesses these URIs and embeds the contents back into the XML document, enabling disclosure of sensitive local files and resources in the context of the LOCAL SERVICE account.

MitigationDisable external entity processing in the XML parser used by the doDocument method by configuring the parser to deny DTDs and external entities, or use a secure XML parser that has XXE protections enabled by default.

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 ViewPower Pro installation and version
    Locate the ViewPower Pro installation directory, typically under C:\Program Files\ViewPower or C:\ViewPower. Check for version information in the application executable, installer logs, or service information. The version can also be identified via the web interface login page or by querying the running service.
    Affected if The installed version matches exactly 2.0-22165 (or falls within the affected range if broader ranges are later identified)
  2. Confirm the doDocument method is exposed
    Identify the web service or API endpoint that exposes the doDocument method. This is typically found in the application's web interface or API service (often on port 8080 or 8081 for ViewPower). Check if the XML handling endpoint is accessible over the network.
    Affected if The web interface or XML endpoint is accessible and accepts XML input without authentication
  3. Verify XML parser configuration for external entity processing
    Examine application configuration files or XML parser settings within the ViewPower installation directory. Look for XML parser configuration that controls DTD and external entity processing. Check if the parser allows external entity resolution.
    Affected if The XML parser configuration permits DTDs and external entity references, or no explicit restriction is configured

You are affected if ViewPower Pro version 2.0-22165 is installed and the web service exposing the doDocument method is accessible, with the XML parser allowing external entity processing.

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

Disable external entity processing in the XML parser used by the doDocument method by configuring the parser to deny DTDs and external entities, or use a secure XML parser that has XXE protections enabled by default.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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