# CVE-2025-1790: Privilege escalation in Genetec Sipelia

> An authenticated low-privileged Windows user can exploit a local privilege escalation vulnerability in the Genetec Sipelia Plugin to gain elevated system privileges.

- **Severity:** Medium 5.8 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:U/CR:H/IR:H/AR:H/MVC:H/MVI:H/MVA:H/MSI:H/MSA:H/S:P/AU:N/V:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Feb 2026
- **Updated:** 13 Feb 2026
- **Also known as:** GHSA-7v9f-f4qv-fcxh

## What is CVE-2025-1790?

CVE-2025-1790 is a medium-severity vulnerability in Genetec Sipelia, published on 13 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Local privilege escalation in Genetec Sipelia Plugin. An authenticated low-privileged Windows user could exploit this vulnerability to gain elevated privileges on the affected system.

Weakness: CWE-250 (Execution with Unnecessary Privileges)

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


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

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

## Is CVE-2025-1790 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-1790 is a medium-severity vulnerability in Genetec Sipelia, published on 13 Feb 2026. 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-1790 in the wild and no public exploit code.

Affected product: Genetec Sipelia. 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-1790/ (Markdown: https://insights.sbomify.com/CVE-2025-1790/index.md)
```

## Sources

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

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