# CVE-2019-25256: VideoFlow Digital Video Protection DVP 2.10 Authenticated Directory Traversal

> Authenticated attackers can read arbitrary system files in VideoFlow DVP by manipulating directory path traversal in download requests.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Dec 2025
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-2gg3-j2hg-72f4

## What is CVE-2019-25256?

CVE-2019-25256 is a high-severity path traversal vulnerability in VideoFlow Ltd. Digital Video Protection DVP, published on 24 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

VideoFlow Digital Video Protection DVP 2.10 contains an authenticated directory traversal vulnerability that allows attackers to access arbitrary system files through unvalidated 'ID' parameters. Attackers can exploit multiple Perl scripts like downloadsys.pl to read sensitive files by manipulating directory path traversal in download requests.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2019-25256 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-25256 is a high-severity path traversal vulnerability in VideoFlow Ltd. Digital Video Protection DVP, published on 24 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25256 exists.

Affected product: VideoFlow Ltd. Digital Video Protection DVP. 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-25256/ (Markdown: https://insights.sbomify.com/CVE-2019-25256/index.md)
```

## Sources

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

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