CVE-2023-31095
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 · uneditedURL Redirection to Untrusted Site ('Open Redirect') vulnerability in CRM Perks Integration for HubSpot and Contact Form 7, WPForms, Elementor, Ninja Forms.This issue affects Integration for HubSpot and Contact Form 7, WPForms, Elementor, Ninja Forms: from n/a through 1.2.8.
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 confidenceAn open redirect vulnerability in the CRM Perks Integration plugin allows attackers to craft malicious URLs that appear to point to the legitimate site but redirect users to attacker-controlled domains. This occurs due to insufficient validation of redirect parameters in the plugin's integration functionality for HubSpot, Contact Form 7, WPForms, Elementor, and Ninja Forms.
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< 1.2.9CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check plugin versionIn WordPress admin, go to Plugins > Installed Plugins and locate 'Crmperks Database For Contact Form 7, Wpforms, Elementor Forms'. The version number is displayed below the plugin name. Alternatively, inspect the main plugin file (usually crmperks.php) and look for the 'Version' header comment.Affected if The installed version is lower than 1.2.9 (e.g., 1.2.8, 1.2.7, etc.)
-
Identify active integrationsIn the WordPress admin, navigate to the CRM Perks plugin settings and review which integrations are enabled. Specifically check for HubSpot, Contact Form 7, WPForms, Elementor Forms, or Ninja Forms integrations that have redirect functionality configured.Affected if Any of the affected integrations (HubSpot, Contact Form 7, WPForms, Elementor, or Ninja Forms) are active with redirect settings configured
-
Test redirect parameter behaviorSubmit a test form using one of the integrated plugins with a redirect URL parameter set to an external domain (e.g., ?redirect=https://attacker.com). Observe whether the application allows redirection to the external domain instead of restricting to internal URLs only.Affected if The application redirects to arbitrary external domains when a redirect parameter is provided, indicating insufficient URL validation
-
Inspect redirect validation codeIf you have access to the plugin source code, examine the file handling redirect logic (typically in includes/ or classes/ directory). Look for functions that process the redirect parameter and check whether they validate that the URL starts with the site domain or is a relative path.Affected if The code passes user-supplied redirect parameters directly to wp_redirect() or similar functions without validating the URL domain or restricting to internal paths
You are affected if the CRM Perks plugin version is below 1.2.9 AND you have any of the HubSpot, Contact Form 7, WPForms, Elementor, or Ninja Forms integrations enabled with redirect functionality that allows external URLs.
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.2.9
Upgrade to a patched version beyond 1.2.8. If no patch is available, implement server-side validation of redirect URLs to ensure they only allow trusted internal domains or relative paths, and avoid passing user-controlled input directly to redirect functions.
1.2.9
- 1. Create a full backup of your WordPress site including database and files
- 2. Navigate to WordPress admin dashboard > Plugins
- 3. Locate the 'CRM Perks Integration for HubSpot and Contact Form 7, WPForms, Elementor, Ninja Forms' plugin
- 4. Click 'Update Now' to upgrade the plugin to version 1.2.9
- 5. Verify the update was successful by checking the installed version number
- 6. Test that form submissions and redirects work correctly
- 7. Clear any caching layers if applicable
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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 $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-31095 — 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-31095 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