# CVE-2019-25563: PCHelpWareV2 1.0.0.5 Denial of Service via SC Creation

> Local attackers can crash PCHelpWareV2 by uploading a malformed BMP file via the Create SC feature, causing a denial of service.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Mar 2026
- **Updated:** 23 Mar 2026
- **Also known as:** GHSA-3962-mh6m-87qj

## What is CVE-2019-25563?

CVE-2019-25563 is a medium-severity denial of service vulnerability in Uvnc PCHelpWareV2, published on 21 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

PCHelpWareV2 1.0.0.5 contains a denial of service vulnerability that allows local attackers to crash the application by supplying a malformed image file. Attackers can trigger the vulnerability through the Create SC feature by selecting a crafted BMP file with an oversized buffer, causing the application to crash.

Weakness: CWE-226 (Sensitive Information in Resource Not Removed Before Reuse)

## Which versions are affected by CVE-2019-25563?

It affects 1 product.


Products: Uvnc Pchelpwarev2.

## How do I fix CVE-2019-25563?

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

## Is CVE-2019-25563 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25563 exists.

## Other vulnerabilities in Uvnc PCHelpWareV2

- [CVE-2019-25564](https://insights.sbomify.com/CVE-2019-25564/): PCHelpWareV2 1.0.0.5 Denial of Service via Group Field (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-25563 and fix it if it is affected.

What it is: CVE-2019-25563 is a medium-severity denial of service vulnerability in Uvnc PCHelpWareV2, published on 21 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25563 exists.

Affected product: Uvnc PCHelpWareV2. 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-2019-25563/ (Markdown: https://insights.sbomify.com/CVE-2019-25563/index.md)
```

## Sources

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

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