# CVE-2025-1316: Edimax IC-7100 IP Camera OS Command Injection

> Attackers can execute arbitrary code on Edimax IC-7100 IP cameras via specially crafted requests due to improper input neutralization.

- **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:** Yes, since 19 Mar 2025 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Mar 2025
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-gjfw-29fg-w4vq

## What is CVE-2025-1316?

CVE-2025-1316 is a critical command injection vulnerability in Edimax IC-7100 IP Camera, published on 4 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Edimax IC-7100 does not properly neutralize requests. An attacker can create specially crafted requests to achieve remote code execution on the device

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Edimax Ic-7100 Firmware.

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

No fix has been published for CVE-2025-1316 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 9 Apr 2025.

## Is CVE-2025-1316 being exploited?

Yes. Attackers have exploited CVE-2025-1316 in the wild since at least 19 Mar 2025.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-1316 is a critical command injection vulnerability in Edimax IC-7100 IP Camera, published on 4 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2025-1316 in the wild since at least 19 Mar 2025.

Affected product: Edimax IC-7100 IP Camera. 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-1316/ (Markdown: https://insights.sbomify.com/CVE-2025-1316/index.md)
```

## Sources

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

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