# CVE-2025-1739: Multiple vulnerabilities in Trivision Camera NC227WF

> Attackers can bypass authentication to retrieve administrator credentials in cleartext from Trivision security cameras.

- **Severity:** High 7.1 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A: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:** 27 Feb 2025
- **Updated:** 27 Feb 2025
- **Also known as:** GHSA-2g33-qx57-xxxh

## What is CVE-2025-1739?

CVE-2025-1739 is a high-severity authentication bypass vulnerability in Trivision Camera NC227WF, published on 27 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An Authentication Bypass vulnerability has been found in Trivision Camera NC227WF v5.8.0 from TrivisionSecurity. This vulnerability allows an attacker to retrieve administrator's credentials in cleartext by sending a request against the server using curl with random credentials to "/en/player/activex_pal.asp" and successfully authenticating the application.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

## Which versions are affected by CVE-2025-1739?


## How do I fix CVE-2025-1739?

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

## Is CVE-2025-1739 being exploited?

There is no known exploitation of CVE-2025-1739 in the wild and no public exploit code.

Public exploit code:

- 0day PoC for CVE-2025-1739 (github_poc): https://github.com/n0n4m3x41/CVE-2025-1739

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-1739 and fix it if it is affected.

What it is: CVE-2025-1739 is a high-severity authentication bypass vulnerability in Trivision Camera NC227WF, published on 27 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-1739 in the wild and no public exploit code.

Affected product: Trivision Camera NC227WF. 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-2025-1739/ (Markdown: https://insights.sbomify.com/CVE-2025-1739/index.md)
```

## Sources

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

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