# CVE-2025-52873: Cognex In-Sight Explorer and In-Sight Camera Firmware Incorrect Permission Assignment for Critical Resource

> A user with protected privileges can modify critical device settings via telnet, bypassing intended security restrictions in Cognex In-Sight cameras.

- **Severity:** High 7.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Sep 2025
- **Updated:** 19 Sep 2025
- **Also known as:** GHSA-922x-wpjc-grx8

## What is CVE-2025-52873?

CVE-2025-52873 is a high-severity missing authorization vulnerability in Cognex In-Sight 2000 series, published on 18 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Cognex In-Sight Explorer and In-Sight Camera Firmware expose 
a telnet-based service on port 23 to allow management operations such as
 firmware upgrades and device reboots, which require authentication. A 
user with protected privileges can successfully invoke the 
SetSystemConfig functionality to modify relevant device properties (such
 as network settings), contradicting the security model proposed in the 
user manual.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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


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

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

## Is CVE-2025-52873 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-52873 is a high-severity missing authorization vulnerability in Cognex In-Sight 2000 series, published on 18 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-52873 in the wild and no public exploit code.

Affected product: Cognex In-Sight 2000 series. 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-52873/ (Markdown: https://insights.sbomify.com/CVE-2025-52873/index.md)
```

## Sources

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

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