# CVE-2023-51591: Voltronic Power ViewPower Pro doDocument XML External Entity Processing Information Disclosure Vulnerability

> Remote attackers can exploit an XML External Entity flaw in ViewPower Pro to disclose sensitive information without authentication.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 May 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-9jwc-9ghq-fgh4

## What is CVE-2023-51591?

CVE-2023-51591 is a medium-severity vulnerability in Voltronic Power ViewPower Pro, published on 3 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

## Which versions are affected by CVE-2023-51591?

It affects 1 product.


Products: Voltronicpower Viewpower.

## How do I fix CVE-2023-51591?

No fix has been published for CVE-2023-51591 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-51591 being exploited?

There is no known exploitation of CVE-2023-51591 in the wild and no public exploit code.

## Other vulnerabilities in Voltronic Power ViewPower Pro

- [CVE-2023-51574](https://insights.sbomify.com/CVE-2023-51574/): Voltronic Power ViewPower updateManagerPassword Exposed Dangerous Method Authentication Bypass Vulnerability (critical 9.8)
- [CVE-2023-51575](https://insights.sbomify.com/CVE-2023-51575/): Voltronic Power ViewPower MonitorConsole Exposed Dangerous Method Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2023-51576](https://insights.sbomify.com/CVE-2023-51576/): Voltronic Power ViewPower Deserialization of Untrusted Data Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2023-51581](https://insights.sbomify.com/CVE-2023-51581/): Voltronic Power ViewPower MacMonitorConsole Exposed Dangerous Method Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2023-51582](https://insights.sbomify.com/CVE-2023-51582/): Voltronic Power ViewPower LinuxMonitorConsole Exposed Dangerous Method Remote Code Execution Vulnerability (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-51591 and fix it if it is affected.

What it is: CVE-2023-51591 is a medium-severity vulnerability in Voltronic Power ViewPower Pro, published on 3 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-51591 in the wild and no public exploit code.

Affected product: Voltronic Power ViewPower Pro. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-51591/ (Markdown: https://insights.sbomify.com/CVE-2023-51591/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-51591
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-51591
- OSV: https://osv.dev/vulnerability/CVE-2023-51591

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-51591/
Summaries are generated and may contain mistakes; the official description above is the record.