CformsiiWordPress extension · Deliciousdays
CVE-2014-9473
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 lib_nonajax.php in the CformsII plugin 14.7 and earlier for WordPress allows remote attackers to execute arbitrary code by uploading a file with an executable extension via the cf_uploadfile2[] parameter, then accessing the file via a direct request to the file in the default upload directory.
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 CformsII WordPress plugin versions 14.7 and earlier contains an unrestricted file upload vulnerability in lib_nonajax.php. Attackers can upload files with executable extensions (such as .php) via the cf_uploadfile2[] parameter to the default WordPress upload directory and then execute them by directly requesting the uploaded file, achieving arbitrary 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
CformsiiWordPress extension
<= 14.7CVSS 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 CformsII plugin installationNavigate to WordPress admin dashboard > Plugins and look for 'CformsII - contactform' or 'Deliciousdays CformsII' in the installed plugins listAffected if CformsII plugin is present in the WordPress installation
-
Determine installed CformsII versionIn Plugins list, locate CformsII and note the version number displayed, or check the plugin's main PHP file header for the Version fieldAffected if Version is 14.7 or lower (the installed version falls within <= 14.7)
-
Verify the vulnerable file existsCheck for the presence of lib_nonajax.php in the plugin directory (typically wp-content/plugins/cforms/lib_nonajax.php)Affected if The file lib_nonajax.php exists in the cforms plugin directory
-
Confirm file upload feature is enabledAccess CformsII settings in WordPress admin (usually under Settings > CformsII) and locate the file upload configuration optionsAffected if File upload functionality is enabled in the plugin settings
A WordPress site is affected if it has CformsII plugin version 14.7 or lower installed with the file upload feature enabled, allowing unauthenticated attackers to upload and execute malicious PHP files.
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 dataImmediately update CformsII to a version newer than 14.7, or disable the plugin until a patched version is available. As a temporary measure, disable file upload functionality in the plugin or add .htaccess rules in the upload directory to prevent execution of uploaded files.
Fix this in Cformsii
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-9473 — 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-9473 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