# CVE-2019-25245: Ross Video DashBoard 8.5.1 Privilege Escalation via Insecure Permissions

> Authenticated users can escalate privileges and execute arbitrary code by replacing the application binary due to insecure file permissions.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Dec 2025
- **Updated:** 5 Mar 2026
- **Also known as:** GHSA-qmhc-vf98-cwmf

## What is CVE-2019-25245?

CVE-2019-25245 is a high-severity vulnerability in Ross Video Ltd. DashBoard, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Ross Video DashBoard 8.5.1 contains an elevation of privileges vulnerability that allows authenticated users to modify executable files due to improper permission settings. Attackers can exploit the 'M' or 'C' flags for 'Authenticated Users' group to replace the DashBoard.exe binary with a malicious executable.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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


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

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

## Is CVE-2019-25245 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-25245 is a high-severity vulnerability in Ross Video Ltd. DashBoard, published on 24 Dec 2025. 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-25245 exists.

Affected product: Ross Video Ltd. DashBoard. 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-25245/ (Markdown: https://insights.sbomify.com/CVE-2019-25245/index.md)
```

## Sources

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

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