Crm Perks FormsWordPress extension · Crmperks
CVE-2024-37463
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 · uneditedMissing Authorization vulnerability in CRM Perks CRM Perks Forms allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects CRM Perks Forms: from n/a through 1.1.5.
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 confidenceCRM Perks Forms plugin versions up to 1.1.5 contain a missing authorization vulnerability that allows attackers to access functionality not properly constrained by access control lists (ACLs). The lack of proper authorization checks permits unauthorized users to perform actions or access sensitive features that should be restricted. With a CVSS score of 9.8, this critical flaw is likely exploitable without authentication.
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.6CVSS 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 plugin versionAccess the WordPress plugins directory and open the Crmperks Crm Perks Forms plugin folder. Open the main PHP file (usually named something like crmperks-forms.php or plugin.php) and look for the 'Version:' header in the plugin comment block. Alternatively, check the readme.txt file for the version number.Affected if The reported version is below 1.1.6
-
Verify plugin installation statusCheck if the Crmperks Crm Perks Forms plugin is active in the WordPress installation by querying the wp_options table for option_name 'active_plugins' or by listing installed plugins via the WordPress admin panel.Affected if The plugin is installed and active, and the version is below 1.1.6
-
Inspect access control implementationExamine the plugin's main PHP files for function calls that handle sensitive operations (form submissions, data exports, user data access). Look for missing capability checks or nonce verification before executing privileged actions.Affected if The plugin code lacks current_user_can() or similar authorization checks before performing sensitive operations
-
Test unauthenticated access to sensitive endpointsUsing a tool like curl or Burp Suite, send requests to common plugin endpoints (such as those handling form data, CRM syncs, or export functions) without providing authentication credentials. Observe whether the requests succeed without returning an authorization error.Affected if Requests to sensitive plugin functions complete successfully without authentication tokens or proper permission validation
The environment is affected if the Crmperks Crm Perks Forms plugin version is below 1.1.6 and sensitive functionality is accessible without authentication.
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.6
Update CRM Perks Forms to the latest version beyond 1.1.5 which should contain the authorization fix. If no patched version is available, disable the plugin or implement server-level access restrictions until remediation is available.
CRM Perks Forms 1.1.6
- Update the CRM Perks Forms plugin to version 1.1.6 or later
- Verify the update was successfully applied by checking the plugin version in WordPress admin
- Confirm the authorization controls are now properly enforced
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
- 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-2024-37463 — 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-37463 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