CformsiiWordPress extension · Cformsii Project
CVE-2015-9333
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 cforms2 plugin before 14.6.10 for WordPress has SQL injection.
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 confidenceSQL injection vulnerability in the cforms2 WordPress plugin (versions before 14.6.10) allows attackers to inject malicious SQL queries through unsanitized user input, potentially enabling unauthorized data access, data modification, or complete database compromise.
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.6.10CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Locate the cforms2 plugin version fileNavigate to /wp-content/plugins/cforms2/ in your WordPress installation and open the main plugin file (usually cforms.php) or look for a version definition in the plugin header commentAffected if The version displayed is lower than 14.6.10 or no version is specified (indicating an old installation)
-
Check plugin version via WordPress adminLog into WordPress admin panel, go to Plugins > Installed Plugins, locate cformsII in the list, and observe the version number displayed under the plugin nameAffected if The version shown is anything less than 14.6.10
-
Verify the plugin is activeIn WordPress admin under Plugins > Installed Plugins, confirm that cformsII shows as 'Active' rather than 'Inactive'Affected if The plugin is active and version is below 14.6.10
-
Inspect the affected SQL query handlerExamine the cforms.php file around line 700-900 where the vulnerable insert_record function processes form data without sanitization, specifically looking for direct use of $_POST or $_GET variables in SQL queriesAffected if Direct SQL queries using unsanitized user input are present in the code
You are affected if the cforms2 plugin is installed, active, and the version is below 14.6.10, as the plugin contains SQL injection vulnerable code processing form submissions.
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.
dbcve · scoped14.6.10
Update cforms2 plugin to version 14.6.10 or later immediately. Given the critical severity (CVSS 9.8), consider taking a backup before updating and monitoring for indicators of compromise.
cforms2 version 14.6.10
- Backup your WordPress site before making any changes
- Navigate to WordPress admin dashboard > Plugins > Installed Plugins
- Locate the cforms2 (Cformsii) plugin
- Click 'Update Now' to update to version 14.6.10
- Alternatively, use WP-CLI: wp plugin update cforms2
- Verify the plugin version shows 14.6.10 after update
- Test that contact forms function correctly after the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Cformsii
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-9333 — 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-9333 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