dbcve.org
Crm Perks FormsWordPress extension · Crmperks

CVE-2024-30498

CRITICAL · 10.0 CVSS v3.1 Published 2024-03-29
Fix available
A fix is available. Upgrade to 1.1.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Improper 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 · moderate confidence

SQL injection vulnerability in CRM Perks Forms plugin allows remote attackers to inject malicious SQL commands via unsanitized user input, potentially enabling unauthorized database access, data exfiltration, or complete application compromise.

MitigationUpgrade CRM Perks Forms beyond version 1.1.4 when a patched version is available; otherwise, implement parameterized queries/prepared statements for all database interactions and validate/sanitize all user-supplied input before incorporating it into SQL queries.

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
Affected:< 1.1.5

CVSS 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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins > locate 'Crmperks Crm Perks Forms' and view the version number displayed under the plugin name
    Affected if The displayed version is lower than 1.1.5 or if the version field is empty/missing (indicating an unpatched or very old installation)
  2. Verify plugin is active
    In WordPress admin > Plugins > Installed Plugins, confirm the 'Crmperks Crm Perks Forms' plugin shows as 'Active'
    Affected if The plugin is active and the version is below 1.1.5, making the vulnerability exploitable
  3. Identify form submission endpoints
    Check the plugin's form settings page in WordPress admin to locate any published forms. Note the form IDs and associated public-facing URLs (typically under /?cf_form= or similar query parameters)
    Affected if Any forms are published and accessible to unauthenticated users, as the SQL injection occurs via unsanitized user input in form submissions
  4. Review server access logs for SQL injection patterns
    Examine web server access logs (apache2/access.log, nginx/access.log, or similar) for requests to form submission endpoints containing SQL operators like UNION, SELECT, OR 1=1, or single quotes in query parameters
    Affected if Log entries show suspicious SQL syntax in parameters related to form submissions, indicating potential exploitation attempts

The environment is affected if the Crmperks Crm Perks Forms plugin is active and its version is below 1.1.5, and any forms are publicly accessible for submission.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.1.5 or later
Fixed in 1.1.5
Interim mitigation

Upgrade CRM Perks Forms beyond version 1.1.4 when a patched version is available; otherwise, implement parameterized queries/prepared statements for all database interactions and validate/sanitize all user-supplied input before incorporating it into SQL queries.

Recommended fix High confidence

Crm Perks Forms version 1.1.5

  1. 1. Backup the entire WordPress site and database before updating.
  2. 2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins.
  3. 3. Find 'Crm Perks Forms' plugin in the list.
  4. 4. Click 'Update now' if an update is available, or manually upload version 1.1.5 of the plugin.
  5. 5. Verify the updated version is 1.1.5 by checking the plugin details.
  6. 6. Test critical form functionalities to ensure the update did not break existing features.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Crm Perks Forms Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-30498 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-30498 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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