Integration For Salesforce And Contact Form 7\, Wpforms\, Elementor\, Ninja FormsWordPress extension · Crmperks

CVE-2023-37982

MEDIUM · 6.1 CVSS v3.1 Published 2023-12-19
Fix available
A fix is available. Upgrade to after 1.3.3 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
URL Redirection to Untrusted Site ('Open Redirect') vulnerability in CRM Perks Integration for Salesforce and Contact Form 7, WPForms, Elementor, Ninja Forms.This issue affects Integration for Salesforce and Contact Form 7, WPForms, Elementor, Ninja Forms: from n/a through 1.3.3.

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

An open redirect vulnerability exists in the CRM Perks Integration plugin where user-supplied parameters are used as redirect targets without proper validation, allowing attackers to craft malicious URLs that appear to point to the legitimate site but redirect users to external malicious sites.

MitigationUpdate to the latest version of the plugin which should contain proper URL validation and whitelisting for redirect destinations, or implement server-side validation to ensure redirect URLs remain within the expected domain.

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
Integration For Salesforce And Contact Form 7\, Wpforms\, Elementor\, Ninja FormsWordPress extension
Affected:<= 1.3.3

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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. Verify CRM Perks Integration plugin is installed
    Check your WordPress site's wp-content/plugins/ directory for a folder named 'crmperks-integration' or similar, or list installed plugins via wp-cli: wp plugin list --status=active --format=csv
    Affected if The plugin is present and active on the WordPress site
  2. Identify the installed plugin version
    Open the main plugin PHP file (usually in wp-content/plugins/crmperks-integration/) and locate the 'Version:' field in the plugin header comment at the top of the file, or check the readme.txt file
    Affected if The version displayed is 1.3.3 or any version lower than 1.3.3
  3. Compare version to affected range
    Review the version number found in step 2 against the affected range: versions 1.3.3 and below
    Affected if The installed version is 1.3.3 or earlier (less than or equal to 1.3.3)
  4. Check for redirect-related functionality
    Search the plugin directory for files containing redirect-related functions (like wp_redirect, wp_safe_redirect, or header() calls) that use query parameters (such as 'redirect', 'url', or 'next') without proper validation
    Affected if The plugin uses user-supplied parameters as redirect targets without domain validation

Your environment is affected if the CRM Perks Integration plugin is installed with version 1.3.3 or lower and utilizes redirect functionality that trusts URL parameters without validating they point to internal domains.

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.

From vendor data
Upgrade available Upgrade to a release after 1.3.3
Interim mitigation

Update to the latest version of the plugin which should contain proper URL validation and whitelisting for redirect destinations, or implement server-side validation to ensure redirect URLs remain within the expected domain.

Fix this in Integration For Salesforce And Contact Form 7\, Wpforms\, Elementor\, Ninja Forms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-37982 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-37982 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