How severe is CVE-2018-10660?

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

Which packages are affected by CVE-2018-10660?

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

How do I fix CVE-2018-10660?

No fixed version has been published for CVE-2018-10660 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-2018-10660 actively exploited in the wild?

Yes. There are 4 known exploit references for CVE-2018-10660, including 1 documented proof-of-concept exploit on Exploit-DB and 3 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2018-10660?

CVE-2018-10660 has an EPSS (Exploit Prediction Scoring System) score of 91.3%, placing it in the 100th 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.

What type of vulnerability is CVE-2018-10660?

CVE-2018-10660 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-2018-10660?

CVE-2018-10660 affects axis a1001 firmware; axis a8004-v firmware; axis a8105-e firmware; axis a9161 firmware, and 386 more product(s). Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2018-10660 published, and has it been updated?

CVE-2018-10660 was published on June 26, 2018 and was last updated on November 21, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2018-10660

CRITICAL

An issue was discovered in multiple models of Axis IP Cameras. There is Shell Command Injection.

Published

Jun 26, 2018

Updated

Nov 21, 2024

Affected

0 pkgs

Patched

None yet

Exploits

4 known

EPSS Exploitation Probability

via FIRST.org ↗

91.3%probability of exploitation in next 30 days

Very High Risk100th percentile+0.27%

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

An issue was discovered in multiple models of Axis IP Cameras. There is Shell Command Injection.

Affected Products

390 products · 390 configurations

a1001 firmwareaxis

< 1.65.1

range

a8004-v firmwareaxis

< 1.65.2

range

a8105-e firmwareaxis

< 1.65.2

range

a9161 firmwareaxis

< 1.65.0

range

a9188 firmwareaxis

< 1.65.0

range

a9188-v firmwareaxis

< 1.65.0

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-45100remotelinux✓ Verified

Axis Network Camera - .srv to parhand Remote Code Execution (Metasploit)

by Metasploit · Jul 27, 2018

Exploit-DB Source

Frequently Asked Questions

An issue was discovered in multiple models of Axis IP Cameras. There is Shell Command Injection.

O3 Security · Impact-Aware SCA

Is CVE-2018-10660 in your stack?

O3 detects CVE-2018-10660 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