# CVE-2019-25240: Missing authorization in DVR

> Unauthenticated attackers can access live video streams from Rifatron DVRs by exploiting the animate.cgi script, leading to privacy violations.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Dec 2025
- **Updated:** 24 Dec 2025
- **Also known as:** GHSA-x3j6-h5jv-f97w

## What is CVE-2019-25240?

CVE-2019-25240 is a high-severity missing authorization vulnerability in Rifatron Co., Ltd. DVR, published on 24 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Rifatron 5brid DVR contains an unauthenticated vulnerability in the animate.cgi script that allows unauthorized access to live video streams. Attackers can exploit the Mobile Web Viewer module by specifying channel numbers to retrieve sequential video snapshots without authentication.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2019-25240 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-25240 is a high-severity missing authorization vulnerability in Rifatron Co., Ltd. DVR, published on 24 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25240 exists.

Affected product: Rifatron Co., Ltd. DVR. 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-25240/ (Markdown: https://insights.sbomify.com/CVE-2019-25240/index.md)
```

## Sources

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

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