Wordpress File UploadWordPress extension · Iptanus
CVE-2015-9341
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 · uneditedThe wp-file-upload plugin before 3.4.1 for WordPress has insufficient restrictions on upload of .php.js files.
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 · moderate confidenceThe wp-file-upload WordPress plugin before version 3.4.1 has insufficient restrictions on file uploads, allowing attackers to upload files with a .php.js double extension. This bypasses basic file type validation by disguising PHP files with a .js extension, potentially enabling remote code execution if the uploaded file can be accessed and executed by the web 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
Wordpress File UploadWordPress extension
< 3.4.1CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
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 wp-file-upload plugin versionNavigate to WordPress admin dashboard > Plugins > Installed Plugins and locate the 'Wordpress File Upload' plugin (by Iptanus). Read the version number displayed under the plugin name.Affected if The installed version is lower than 3.4.1 (e.g., 3.4.0, 3.3.x, etc.)
-
Locate plugin files on serverIf you have filesystem access, check the plugin directory at wp-content/plugins/wp-file-upload/ and locate the main plugin file (often wp-file-upload.php or similar) to read the version declared in the plugin header.Affected if The version in the plugin header is below 3.4.1
-
Verify if file upload endpoint existsCheck if the plugin's upload functionality is accessible by looking for upload-related pages or endpoints in WordPress admin, or by checking for files like 'wp-file-upload.php' or 'php-file-upload' directories under wp-content/plugins/.Affected if The plugin is installed and active, creating an accessible file upload interface
-
Test file type validation restrictionsIf you have authorization to test, attempt to upload a file with a double extension such as 'test.php.js' through the plugin's upload form. Observe whether the upload is accepted or rejected.Affected if The upload is accepted without proper validation, allowing double extensions or potentially executable file types like .php
A system is affected if the wp-file-upload plugin version is below 3.4.1 and the file upload functionality is active and accessible.
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 data3.4.1
Upgrade the wp-file-upload plugin to version 3.4.1 or later which implements proper file type validation and restricts dangerous file extensions.
Fix this in Wordpress File Upload
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-9341 — 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-2015-9341 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