Contact Form GeneratorWordPress extension · Creative Solutions
CVE-2023-35911
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 · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Creative Solutions Contact Form Generator : Creative form builder for WordPress allows SQL Injection.This issue affects Contact Form Generator : Creative form builder for WordPress: from n/a through 2.6.0.
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 confidenceA SQL injection vulnerability exists in the Contact Form Generator WordPress plugin (versions through 2.6.0) due to improper neutralization of special elements in SQL commands. This critical (CVSS 9.8) flaw allows remote attackers to inject malicious SQL queries through unsanitized input fields in the plugin's forms, potentially enabling data exfiltration 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
Contact Form GeneratorWordPress extension
<= 2.6.0CVSS 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.
-
Check installed plugin versionIn WordPress admin, go to Plugins > Contact Form Generator and verify the version number displayed, or check the plugin header in wp-content/plugins/contact-form-generator/main.php for the 'Version' tagAffected if The displayed version is 2.6.0 or lower
-
Confirm plugin is activeVerify the Contact Form Generator plugin status in WordPress admin under Plugins > Installed Plugins; a check of database table wp_options for option_name='active_plugins' can also confirm if plugin is enabledAffected if Plugin is installed and active with version <= 2.6.0
-
Identify published formsCheck for any contact forms created with the plugin by reviewing post type 'contact_form_generator' in wp_posts table or through the plugin's admin interface under Contact Form Generator menuAffected if Any forms exist in the system, as the SQL injection occurs through unsanitized input fields in these forms
-
Review database for suspicious query patternsExamine MySQL slow query log or general log for SQL injection patterns in INSERT/UPDATE operations on tables related to the plugin; look for UNION SELECT, OR 1=1, or other SQL meta-characters in form submission dataAffected if Unusual SQL syntax or unexpected UNION/SELECT statements appear in form-related database queries
The environment is affected if the Contact Form Generator plugin is installed, active, and running at version 2.6.0 or lower with any published forms.
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 Contact Form Generator plugin to the latest patched version immediately. If no patch is available, disable the plugin until a fix is released, and implement web application firewall rules to block SQL injection attack patterns.
Fix this in Contact Form Generator
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35911 — 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-2023-35911 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