How severe is CVE-2017-11366?

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

Which packages are affected by CVE-2017-11366?

CVE-2017-11366 affects the following packages: codiad/codiad (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2017-11366?

Update codiad/codiad to 2.8.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-11366 is resolved across your whole dependency graph.

How do I detect CVE-2017-11366 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for codiad/codiad, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2017-11366 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is CVE-2017-11366 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2017-11366, including 1 in-the-wild exploitation 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-2017-11366?

CVE-2017-11366 has an EPSS (Exploit Prediction Scoring System) score of 7.5%, placing it in the 95th 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. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2017-11366?

CVE-2017-11366 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.

When was CVE-2017-11366 published, and has it been updated?

CVE-2017-11366 was published on August 21, 2017 and was last updated on October 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

CRITICAL severity

CVE-2017-11366 — codiad

CRITICALFix: Codiad/Codiad#1013

CVE-2017-11366 is a critical-severity (CVSS 9.8) OS Command Injection vulnerability in codiad/codiad. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for codiad/codiad — see the affected versions and patch details below.

Codiad Vulnerable to Shell Command Injection

Also known asGHSA-jccv-3h4x-35mv

Published

Aug 21, 2017

Updated

Oct 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Oct 31, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

7.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs95th percentile — riskier than 95% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐘codiad/codiad

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

components/filemanager/class.filemanager.php in Codiad before 2.8.4 is vulnerable to remote command execution because shell commands can be embedded in parameter values, as demonstrated by search_file_type.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`codiad/codiad`	all versions	2.8.3`composer require codiad/codiad:^2.8.3`

Affected Products

1 product · 1 configurations

Application

codiadcodiad

≤ 2.8.3

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.

components/filemanager/class.filemanager.php in Codiad before 2.8.4 is v…

jianshu.comNVDOct 2019

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for codiad/codiad, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update codiad/codiad to 2.8.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-11366 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2017-11366 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

9.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CWE Classification

CWE-78OS Command Injection

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

OpenSSF Scorecard

Package health score

Codiad

3.1/10

Maintained0/10

Code-Review4/10

Branch-ProtectionN/A

Assessed Oct 26, 2026

Timeline

Disclosed

Aug 21, 2017

First exploit

Oct 3, 2019

Last updated

Oct 20, 2026

Identifiers

CVE-2017-11366

GHSA-jccv-3h4x-35mv

References

Advisorygithub.com Advisorygithub.com Advisorynvd.nist.gov · CVE 2017 11366 Fixgithub.com · b3645b4c6718cef6de7003f41aafe7bfcc0395d1 Webgithub.com · ca5089eeba42d16ce3a7f86be628ac7750780111 Packagegithub.com · Codiad Evidencejianshu.com · 41ac7ac2a7af

Related vulnerabilities

Also affects codiad/codiad

This CVE is critical severity; 2 of 7 other CVEs affecting codiad/codiad are rated as high or higher (top: critical).

CVE-2017-20178CVE-2020-14043CVE-2020-23355CVE-2020-14044CVE-2020-14042CVE-2018-14009CVE-2019-19208

Same weakness: CWE-78

This CVE is critical severity — higher than any of the other 1 CVE with CWE-78 (highest there: high).

CVE-2026-33050Browse all CWE-78

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 20, 2026

CVE-2017-11366 — codiad

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2017-11366 in your dependencies?