How severe is CVE-2025-1316?

CVE-2025-1316 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2025-1316?

Affected package information for CVE-2025-1316 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2025-1316?

No fixed version has been published for CVE-2025-1316 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2025-1316 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-1316 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-1316?

CVE-2025-1316 has an EPSS (Exploit Prediction Scoring System) score of 86.7%, placing it in the 99th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2025-1316 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2025-1316 (Edimax IC-7100 IP Camera OS Command Injection Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2025-03-19. CISA required all US federal civilian agencies to remediate this vulnerability by 2025-04-09. The required action was: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2025-1316?

CVE-2025-1316 is classified as OS Command Injection (CWE-78). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Which products and versions are affected by CVE-2025-1316?

CVE-2025-1316 affects edimax ic-7100 firmware. Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2025-1316 published, and has it been updated?

CVE-2025-1316 was published on March 5, 2025 and was last updated on October 30, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2025-03-19 — agencies required to remediate by 2025-04-09

CVE-2025-1316

CRITICAL

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

Published

Mar 5, 2025

Updated

Oct 30, 2025

Affected

0 pkgs

Patched

None yet

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

86.7%probability of exploitation in next 30 days

Very High Risk99th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

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

Affected Products

1 product · 1 configurations

ic-7100 firmwareedimax

all

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is CVE-2025-1316 in your stack?

O3 detects CVE-2025-1316 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works