CVE-2014-0342
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMultiple unrestricted file upload vulnerabilities in fileupload.php in PivotX before 2.3.9 allow remote authenticated users to execute arbitrary PHP code by uploading a file with a (1) .php or (2) .php# extension, and then accessing it via unspecified vectors.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencePivotX before version 2.3.9 contains unrestricted file upload vulnerabilities in fileupload.php. Authenticated users can upload files with executable extensions like .php or .php# which are not properly validated, allowing them to upload malicious PHP scripts and achieve arbitrary code execution on the server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2.3.8= 2.1.0= 2.1.1= 2.1.2= 2.2.0= 2.2.1= 2.2.2= 2.2.3= 2.2.5= 2.3.0= 2.3.2= 2.3.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify PivotX versionLocate the version file or admin panel that displays the installed PivotX version. Common locations include a version.php file, changelog, or the admin dashboard.Affected if Installed version is 2.1.0, 2.1.1, 2.1.2, 2.2.0, 2.2.1, 2.2.2, 2.2.3, 2.2.5, 2.3.0, 2.3.2, 2.3.3, or any version 2.3.8 or lower.
-
Verify fileupload.php existsSearch the web root for the fileupload.php script. This is the vulnerable component referenced in the CVE.Affected if fileupload.php exists in the application directory.
-
Confirm user authentication is enabledCheck if PivotX user accounts are configured and authentication is active. The vulnerability requires an authenticated user to exploit.Affected if PivotX has at least one user account and login functionality is operational.
-
Inspect upload directories for executable filesExamine directories where PivotX stores uploaded files. Look for .php, .php5, .phtml, or files with .php# extensions that could bypass filters.Affected if Any PHP files or files with executable extensions are present in upload directories.
-
Review file upload configurationCheck PivotX settings to see if file upload functionality is enabled and what file types are permitted.Affected if File uploads are enabled and no strict allow-list validation is configured.
You are affected if your PivotX version is 2.3.8 or lower, fileupload.php exists, and authenticated users can upload files without proper extension validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to PivotX 2.3.9 or later which implements proper file extension validation and blocks executable file uploads. Additionally, implement strict allow-list validation for permitted file types and store uploads outside web-accessible directories.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0342 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-0342 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data