How severe is CVE-2014-8739?

No CVSS score has been assigned to CVE-2014-8739 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2014-8739?

CVE-2014-8739 affects the following packages: blueimp/jquery-file-upload (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2014-8739?

No patched version of blueimp/jquery-file-upload has shipped for CVE-2014-8739 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect CVE-2014-8739 in my Packagist dependencies?

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

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

Treat uploaded files as untrusted until proven otherwise: validate the actual content type rather than the supplied extension, store uploads outside the web root on a volume mounted without execute permission, and rename them to server-generated identifiers so an attacker cannot choose the path a request will later resolve.

Is CVE-2014-8739 actively exploited in the wild?

Yes. There are 5 known exploit references for CVE-2014-8739, including 2 documented proof-of-concept exploits 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-2014-8739?

CVE-2014-8739 has an EPSS (Exploit Prediction Scoring System) score of 91.7%, 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-2014-8739?

CVE-2014-8739 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-2014-8739?

A Nuclei detection template exists for CVE-2014-8739, 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-2014-8739 published, and has it been updated?

CVE-2014-8739 was published on May 17, 2022 and was last updated on April 25, 2024. 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

CVE-2014-8739 — jquery-file-upload

CVE-2014-8739 is a Unrestricted File Upload vulnerability in blueimp/jquery-file-upload. 5 public exploit references exist, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.

jQuery File Upload Plugin Unrestricted file upload vulnerability

Published

May 17, 2022

Updated

Apr 25, 2024

Affected

1 pkg

Patched

See advisory

Exploits

5 known

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

EPSS Exploitation Probability

via FIRST.org ↗

91.7%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

🐘blueimp/jquery-file-upload

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

Unrestricted file upload vulnerability in server/php/UploadHandler.php in the jQuery File Upload Plugin 6.4.4 for jQuery, as used in the Creative Solutions Creative Contact Form (formerly Sexy Contact Form) before 1.0.0 for WordPress and before 2.0.1 for Joomla!, allows remote attackers to execute arbitrary code by uploading a PHP file with an PHP extension, then accessing it via a direct request to the file in files/, as exploited in the wild in October 2014.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`blueimp/jquery-file-upload`	all versions	No fix

Affected Products

2 products · 3 configurations

Application

creative contact formcreative-solutions

< 2.0.1

range

Application

jquery file uploadjquery_file_upload_project

1 version

6.4.4

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-35057webappsphp

WordPress Plugin 0.9.7 / Joomla! Component 2.0.0 Creative Contact Form - Arbitrary File Upload

by Claudio Viviani · Oct 25, 2014

Exploit-DB Source

EDB-36811remotephp✓ Verified

WordPress Plugin Creative Contact Form - Arbitrary File Upload (Metasploit)

by Metasploit · Apr 21, 2015

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/jquery-file-upload, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of blueimp/jquery-file-upload has shipped for CVE-2014-8739 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
Treat uploaded files as untrusted until proven otherwise: validate the actual content type rather than the supplied extension, store uploads outside the web root on a volume mounted without execute permission, and rename them to server-generated identifiers so an attacker cannot choose the path a request will later resolve.

How to detect CVE-2014-8739

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2014-8739 -u https://target

Template: WordPress Sexy Contact Form (<= 0.9.7) - Arbitrary File Upload
Severity: critical
Impact: Attackers can execute arbitrary PHP code on the server, leading to full system compromise.
Remediation: Update to the latest version of the plugin that fixes this issue or implement server-side validation to restrict file types.

Template by ProjectDiscovery nuclei-templates (melmathari), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

Unrestricted file upload vulnerability in `server/php/UploadHandler.php` in the jQuery File Upload Plugin 6.4.4 for jQuery, as used in the Creative Solutions Creative Contact Form (formerly Sexy Contact Form) before 1.0.0 for WordPress and before 2.0.1 for Joomla!, allows remote attackers to execute arbitrary code by uploading a PHP file with an PHP extension, then accessing it via a direct request to the file in `files/`, as exploited in the wild in October 2014.

O3 Security · Impact-Aware SCA

Is CVE-2014-8739 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works