How severe is CVE-2018-9206?

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

Which packages are affected by CVE-2018-9206?

CVE-2018-9206 affects the following packages: blueimp-file-upload (npm). Ecosystems affected: npm.

How do I fix CVE-2018-9206?

Update blueimp-file-upload to 9.22.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-9206 is resolved across your whole dependency graph.

How do I detect CVE-2018-9206 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for blueimp-file-upload. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

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

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2018-9206?

O3 pinpoints whether CVE-2018-9206 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2018-9206 actively exploited in the wild?

Yes. There are 17 known exploit references for CVE-2018-9206, including 3 documented proof-of-concept exploits on Exploit-DB and 11 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-9206?

CVE-2018-9206 has an EPSS (Exploit Prediction Scoring System) score of 97.1%, 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-9206?

CVE-2018-9206 is classified as Unrestricted File Upload (CWE-434). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for CVE-2018-9206?

A Nuclei detection template exists for CVE-2018-9206, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

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

CVE-2018-9206 was published on October 11, 2018 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

CVE-2018-9206

CRITICAL

Unrestricted Upload of File with Dangerous Type in blueimp-file-upload

Also known asGHSA-4cj8-g9cp-v5wr

Published

Oct 11, 2018

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

17 known

EPSS Exploitation Probability

via FIRST.org ↗

97.1%probability of exploitation in next 30 days

Very High Risk100th 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.

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

blueimp-file-uploadnpm

121Kdownloads / week

Description

Unauthenticated arbitrary file upload vulnerability in Blueimp jQuery-File-Upload <= v9.22.0

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`blueimp-file-upload`	all versions	9.22.1

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-45584webappsphp✓ Verified

jQuery-File-Upload 9.22.0 - Arbitrary File Upload

by Larry W. Cashdollar · Oct 11, 2018

Exploit-DB Source

EDB-46182webappsphp

Blueimp's jQuery File Upload 9.22.0 - Arbitrary File Upload Exploit

by Larry W. Cashdollar · Jan 16, 2019

Exploit-DB Source

EDB-45790remotephp✓ Verified

blueimp's jQuery 9.22.0 - (Arbitrary) File Upload (Metasploit)

by Metasploit · Nov 6, 2018

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for blueimp-file-upload. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update blueimp-file-upload to 9.22.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-9206 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2018-9206 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2018-9206. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Unauthenticated arbitrary file upload vulnerability in Blueimp jQuery-File-Upload <= v9.22.0

O3 Security · Impact-Aware SCA

Is CVE-2018-9206 in your dependencies?

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

Scan my dependencies How O3 SCA works

CVE-2018-9206

EPSS Exploitation Probability

Blast Radius

Description

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is CVE-2018-9206 in your dependencies?