N Media File UploaderWordPress extension · Najeebmedia
CVE-2014-5324
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 · uneditedUnrestricted file upload vulnerability in the N-Media file uploader plugin before 3.4 for WordPress allows remote authenticated users to execute arbitrary PHP code by leveraging Author privileges to store a file.
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 confidenceThe N-Media file uploader plugin before version 3.4 for WordPress contains an unrestricted file upload vulnerability that allows authenticated users with Author privileges to upload arbitrary files, including PHP scripts that can be executed for remote code execution.
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
N Media File UploaderWordPress extension
<= 3.3= 3.0= 3.1= 3.2CVSS 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
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/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.
-
Confirm N-Media File Uploader plugin is installedNavigate to WordPress admin dashboard under Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for a folder named 'nm-file-uploader' or similar N-Media related foldersAffected if The plugin is present in the WordPress installation
-
Identify the installed plugin versionAccess the plugin file (typically nm-file-uploader.php or similar) in the plugin folder and locate the version header comment, or view the version displayed in the WordPress Plugins admin pageAffected if The version listed is 3.0, 3.1, 3.2, or 3.3 (any version 3.3 or lower)
-
Verify the upload functionality is accessibleCheck if the plugin's upload shortcode or widget is actively used on the site, or verify the plugin admin settings page is accessible and the upload feature is enabledAffected if The plugin is active and the file upload feature is enabled on the site
-
Confirm presence of user accounts with Author role or higherIn WordPress admin, go to Users > All Users and review user roles; check wp_users and wp_usermeta database tables if admin access is limitedAffected if Any user account has Author, Editor, or Administrator role, allowing authentication to access the upload functionality
A user is affected if the N-Media File Uploader plugin versions 3.0 through 3.3 are installed and active on the WordPress site, and any authenticated user with Author-level permissions exists.
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 dataUpdate the N-Media file uploader plugin to version 3.4 or later, which includes proper file type validation and restrictions. Alternatively, remove the plugin if not required and implement file upload restrictions at the web server level.
Fix this in N Media File Uploader
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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 $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-5324 — 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-5324 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