# CVE-2019-25236: iSeeQ Hybrid DVR WH-H4 1.03R Unauthenticated Live Stream Disclosure

> Attackers can access live video streams and snapshots from iSeeQ Hybrid DVRs without authentication via the get_jpeg endpoint.

- **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-pmc3-hmfh-583m

## What is CVE-2019-25236?

CVE-2019-25236 is a high-severity missing authorization vulnerability in iSeeQ Hybrid DVR WH-H4, published on 24 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

iSeeQ Hybrid DVR WH-H4 1.03R contains an unauthenticated vulnerability in the get_jpeg script that allows unauthorized access to live video streams. Attackers can retrieve video snapshots from specific camera channels by sending requests to the /cgi-bin/get_jpeg endpoint without authentication.

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

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


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

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

## Is CVE-2019-25236 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-25236 is a high-severity missing authorization vulnerability in iSeeQ Hybrid DVR WH-H4, 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-25236 exists.

Affected product: iSeeQ Hybrid DVR WH-H4. 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-25236/ (Markdown: https://insights.sbomify.com/CVE-2019-25236/index.md)
```

## Sources

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

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