# CVE-2025-25504: Command injection in n/a

> Attackers can execute arbitrary commands with root privileges on Gefen WebFWC devices via an unauthenticated TCP connection.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 May 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-5ggr-xpwv-2fq3

## What is CVE-2025-25504?

CVE-2025-25504 is a medium-severity command injection vulnerability in n/a, published on 5 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in the /usr/local/bin/jncs.sh script of Gefen WebFWC (In AV over IP products) v1.85h, v1.86v, and v1.70 allows attackers with network access to connect to the device over TCP port 4444 without authentication and execute arbitrary commands with root privileges.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command), CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Niceforyou Gefen Webfwc.

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

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

## Is CVE-2025-25504 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-25504 is a medium-severity command injection vulnerability in n/a, published on 5 May 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-2025-25504 exists.

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

## Sources

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

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