Integration For Contact Form 7 And Zoho Crm\, BiginWordPress extension · Crmperks
CVE-2023-25976
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in CRM Perks Integration for Contact Form 7 and Zoho CRM, Bigin plugin <= 1.2.2 versions.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the CRM Perks Integration plugin for Contact Form 7 and Zoho CRM/Bigin allows attackers to trick authenticated users into performing unintended actions due to missing or improper CSRF token validation on plugin functions.
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 Contact Form 7 And Zoho Crm\, BiginWordPress extension
<= 1.2.2CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 CRM Perks Integration plugin filesCheck your WordPress installation under wp-content/plugins/ for a folder named 'crmperks-integration' or similar, and open the main plugin PHP file to view the plugin header which contains the version numberAffected if The plugin version listed in the header is 1.2.2 or lower
-
Verify the installed version against affected rangeCompare the version found in the plugin header to the affected range: any version less than or equal to 1.2.2 is vulnerableAffected if The version displayed is 1.2.2 or any earlier version number such as 1.2.1, 1.2.0, or 1.0.0
-
Confirm the plugin is currently activeIn the WordPress admin dashboard, go to Plugins > Installed Plugins and check whether the CRM Perks Integration plugin is activatedAffected if The plugin shows as Active and the version is 1.2.2 or below - only active installations with vulnerable versions can be exploited
-
Check for CSRF protection implementationExamine the plugin source code for nonce verification by searching for 'wp_verify_nonce', 'check_admin_referer', or 'check_ajax_referer' functions used in form submissions and admin action handlersAffected if No nonce verification is found in the plugin code handling form submissions or admin actions, indicating CSRF protection is missing
Your environment is affected if the CRM Perks Integration plugin for Contact Form 7 and Zoho CRM/Bigin is installed, active, and running version 1.2.2 or lower without proper nonce/CSRF token validation in its action handlers.
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.
From vendor dataUpdate the plugin to version 1.2.3 or later which includes anti-CSRF token implementation; alternatively, ensure all form submissions and admin actions include proper nonce verification and SameSite cookie attributes.
Fix this in Integration For Contact Form 7 And Zoho Crm\, Bigin
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-25976 — 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-25976 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