# CVE-2025-2080: Auth bypass in Optigo Visual Networks Capture Tool

> Attackers can bypass authentication via an exposed web service to gain control over utilities in Optigo Networks capture tools.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/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:** 13 Mar 2025
- **Updated:** 26 Aug 2026
- **Also known as:** GHSA-jqj3-fh4v-x7hj

## What is CVE-2025-2080?

CVE-2025-2080 is a critical authentication bypass vulnerability in Optigo Visual Networks Capture Tool, published on 13 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Optigo Networks Visual BACnet Capture Tool and Optigo Visual Networks Capture Tool version 3.1.2rc11 contain an exposed web management service that could allow an attacker to bypass authentication measures and gain controls over utilities within the products.

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

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


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

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

## Is CVE-2025-2080 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2080 is a critical authentication bypass vulnerability in Optigo Visual Networks Capture Tool, published on 13 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-2080 in the wild and no public exploit code.

Affected product: Optigo Visual Networks Capture Tool. 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-2080/ (Markdown: https://insights.sbomify.com/CVE-2025-2080/index.md)
```

## Sources

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

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