Edimax IC-7100 IP Camera OS Command Injection (CVE-2025-1316)
Published In CISA KEV since Sources: pwn.watch, CVE.org, CISA ICS
What is affected, what to do
The Edimax IC-7100 IP camera has an OS command injection vulnerability that allows an attacker to achieve remote code execution through specially crafted requests. This vulnerability is actively exploited in the wild, necessitating immediate action. All versions of the Edimax IC-7100 are affected, and the product may be end-of-life or end-of-service. Users should discontinue using the product immediately as no patches are available. The urgency to respond is high due to its exploitation in active attack campaigns.
The vulnerability is being actively exploited; treat it as a priority. The available sources name no fixed version. Check the vendor guidance in the references below. Immediate actions, mitigation and detection rules are in the runbook below.
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
9.8
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: NVD, CVSS v3
9.8
CVSS v3
Severity Critical on the scale from 0 to 10.
Source: pwn.watch, CVE.org, CISA ICS
74.5 %
EPSS score
High — model estimates ≥ 50% chance of real-world exploitation within 30 days.
Source: FIRST EPSS, percentile 99.50
Show all metrics
- Severity
- Critical
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 236.20 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- actively exploitedSource: VulnCheck KEV (opens in a new tab) How we classify
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 9.8 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 9.8
CVSS v4
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 9.3
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 74.5 %
- High — model estimates ≥ 50% chance of real-world exploitation within 30 days.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 99.50
- Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- Actively exploited
- Published
In CISA KEV since
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- CISA assessment (SSVC)
- Exploitation: active · automatable · Technical impact: total
- Source: CISA Vulnrichment, as of 19 March 2025
CWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-78
Response and mitigation
Why act now?
Prioritisation rationale
This CVE is on KEV because the combination of a network-exposed consumer IP camera, unauthenticated remote code execution and EoL status creates an ideal long-term recruiting pool for IoT botnets — exploitation likelihood sits near the top of the current KEV list. Attackers mass-scan the internet for Edimax fingerprints and enlist compromised cameras into Mirai variants for DDoS, residential-proxy services and lateral pivots into internal networks. For European organisations the exposure is high wherever cameras sit at perimeter sites (reception, car park, branch offices) and are reachable through port-forwarding; purely internal VLANs without internet egress carry lower compromise risk, but the NIS2 compliance pressure for an EoL device remains. Priority: plan replacement, kill internet exposure today.
Runbook step 1
Immediate response (0-24 h)
- Inventory every Edimax IC-7100 on the estate (Nmap for banner "Edimax", HTTP title "IC-7100", Edimax Technology OUI). CISA confirms the product is EoL/EoS — there will be no vendor patch, so the default path is decommissioning, not patching.
- Pull the cameras off the public internet immediately: remove port-forwards (UDP/80, 443, 10554, 5555), UPnP mappings on perimeter routers, and any DynDNS registrations. Run a Shodan/Censys query against your own ASN to find forgotten exposures.
- Move affected cameras into an isolated management VLAN with no internet egress; if video must still reach remote viewers, terminate the stream on a hardened reverse-proxy or NVR with its own authentication layer.
- Rotate admin credentials on every Edimax camera and check for reuse elsewhere (password-spraying follow-on risk).
- Raise a change ticket for hardware replacement — plan migration to a currently supported ONVIF model with signed firmware and record the end-of-life event in the asset register (needed as NIS2 evidence).
Runbook step 2
Mitigation layers
- Network segmentation: dedicated IoT/OT VLAN, ACL that permits only inbound traffic from the NVR/VMS host to the camera streaming port, no outbound traffic other than NTP to an internal server.
- Perimeter: WAF or reverse proxy in front of any camera web UI that must remain reachable. Block requests that contain shell metacharacters (;, |, &&, `, $(, %0a) in query parameters and POST bodies — this directly addresses the command-injection class.
- IPS: enable Snort/Suricata signatures from ET Open or vendor-neutral feeds targeting "Edimax IC-7100 command injection"; at minimum pattern-match on suspicious CGI paths combined with shell metacharacters.
- Egress filtering: cameras must not initiate outbound connections to arbitrary internet IPs. Default-deny with an allowlist for internal NTP/Syslog/NVR only. This stops reverse shells and botnet C2 callbacks after a successful RCE.
- Service hardening: disable Telnet, UPnP and the "Edimax Plug & View" cloud service on the device itself where the firmware UI still allows it.
- If decommissioning cannot be completed immediately, record the compensating control in the risk register, obtain CISO sign-off on residual risk and set a firm hardware-replacement deadline (recommended < 90 days).
Runbook step 3
Detection rules
- Zeek/Suricata: HTTP requests to camera IPs with URL or body payloads containing shell metacharacters (
http.uri contains ";" OR "|" OR "%60" OR "$("). Sigma sketch:detection: selection: http.method: POST; http.uri|contains: ['/camera-cgi/', '/goform/']; http.request_body|re: '[;|&$]'`. - Netflow/firewall logs: outbound connections from camera-VLAN IPs on ports other than NTP/Syslog, especially IRC-style ports (6660-6669), Tor guard nodes, or any TCP flow to hosting ASNs — classic Mirai/Gafgyt post-exploitation behaviour on IoT devices.
- DNS telemetry: lookups from camera IPs to DGA-like domains or known IoT-botnet C2 lists (e.g. abuse.ch feeds). KQL sketch:
DnsEvents | where ClientIP in (CameraIPs) | where Name !endswith "edimax.com" and Name !endswith "<internal_domain>". - Camera syslog (if available): repeated login failures, process starts outside the standard daemon list, unexpected reboots.
- Perimeter scan detection: external scans aimed at camera web ports with user agents from known IoT scan tools (Mozi, zgrab, masscan). Hits are a strong indicator of active enumeration against your estate.
- Zeek/Suricata: HTTP requests to camera IPs with URL or body payloads containing shell metacharacters (
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
Edimax IC-7100 does not properly neutralize requests. An attacker can create specially crafted requests to achieve remote code execution on the device
Source: pwn.watch, NVD (NIST), cvelistv5, CISA KEV Catalog, cisa_ics_advisory, CVE.org (MITRE)
Vendors and products
Affected operating systems
| Other | edimax | ic-7100_firmware | — |
Weakness classes (CWE)
CWE-78Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Base
The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component.
Entry at MITRE CWE-78
Public exploit references
Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.
| CISA KEV Catalog | CISA Known Exploited Vulnerability (opens in a new tab)cisa.gov | actively exploited |
References & sources
- cisa.govnews-events/ics-advisories/icsa-25-063-08Mitigation, Third-party advisory, US government resource
- cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2025-1316government-resource, US government resource
- pwn.watchpwn.watch: Edimax IC-7100 IP Camera: IC-7100 IP Camera OS Command Injection Vulnerabilitypwn-watch
- edimax.comEdimax advisory: Edimax IC-7100 IP Camerapwn-watch
- NVD (NIST)NVD: CVE-2025-1316pwn-watch
- cisa.govCISA Known Exploited Vulnerabilities Catalogpwn-watch
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2025-1316"><img src="https://intel.neosec.eu/badge/cve/CVE-2025-1316.svg?lang=en" alt="CVE-2025-1316 – NEOSEC Intel" height="20"></a>