Crm Perks FormsWordPress extension · Crmperks
CVE-2024-30499
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 CRM Perks CRM Perks Forms.This issue affects CRM Perks Forms: from n/a through 1.1.4.
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 CRM Perks Forms WordPress plugin (versions up to 1.1.4) allows unauthenticated attackers to inject malicious SQL commands through unsanitized user input fields, potentially allowing data exfiltration or 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
Crm Perks FormsWordPress extension
< 1.1.5CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 versionNavigate to WordPress Admin > Plugins > Installed Plugins, locate 'Crmperks Crm Perks Forms' or 'CRM Perks Forms', and note the version number displayed. Alternatively, inspect the plugin's main PHP file header (e.g., crm-perks-forms.php) for the 'Version' tag.Affected if Version is 1.1.4 or lower (less than 1.1.5)
-
Confirm plugin is activeIn WordPress Admin > Plugins, verify whether the CRM Perks Forms plugin shows as 'Active' rather than 'Inactive' or 'Must Use'.Affected if Plugin is installed AND active with a vulnerable version (< 1.1.5)
-
Identify exposed input endpointsReview the plugin's source code for form handlers, specifically files processing user-submitted data (common locations: includes/ folder, main plugin file). Look for direct usage of $_POST, $_GET, or $_REQUEST without prepare() statements or sanitization functions.Affected if Plugin contains form processing code that handles user input without parameterized queries
-
Verify database interaction patternsSearch plugin PHP files for SQL queries using $wpdb->query(), $wpdb->get_results(), or similar, checking whether user input is passed directly into query strings without $wpdb->prepare().Affected if Direct SQL queries accept unsanitized user input from request parameters
You are affected if CRM Perks Forms plugin version is below 1.1.5 AND the plugin is active, with form input fields that feed into unprotected database queries.
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 · scoped1.1.5
Update to the latest version of CRM Perks Forms when available, or implement proper input validation and use prepared statements/parameterized queries for all database interactions.
1.1.5
- Backup your WordPress site and database before performing any updates
- Update the CRM Perks Forms plugin to version 1.1.5 or later via the WordPress admin panel under Plugins > All Plugins, or via FTP/manual upload
- Verify the update was successful by checking the installed plugin version
- Test that form creation and submission functionality works correctly after the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Crm Perks Forms
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-2024-30499 — 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-2024-30499 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