Bigcontact Contact PageWordPress extension · Bigcontact Contact Page Project
CVE-2023-22694
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 Arian Khosravi, Norik Davtian BigContact Contact Page plugin <= 1.5.8 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 · moderate confidenceA CSRF vulnerability exists in the BigContact Contact Page WordPress plugin versions 1.5.8 and below. Attackers can craft malicious requests that trick authenticated administrators into performing unintended actions (such as modifying plugin settings or contact form configurations) without their knowledge, due to missing or inadequate anti-CSRF token validation on state-changing operations.
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
Bigcontact Contact PageWordPress extension
<= 1.5.8CVSS 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.
-
Check the installed plugin versionNavigate to WordPress Admin > Plugins > Installed Plugins. Find 'Bigcontact Contact Page' (or 'BigContact Contact Page') in the list and note the version number displayed below the plugin name.Affected if The displayed version is 1.5.8 or lower (e.g., 1.5.7, 1.5.6, 1.5.5, etc.)
-
Confirm the plugin is activeIn the same Plugins screen, verify that BigContact Contact Page shows as 'Active' under the plugin status column.Affected if The plugin is active and in use on the WordPress site.
-
Inspect admin forms for nonce fieldsAccess the plugin settings page (usually under 'BigContact' or 'Contact' in the WordPress admin sidebar). Right-click the page, select 'View Page Source,' and search for occurrences of 'wp_nonce' or '_wpnonce' within the HTML.Affected if No nonce fields are found in any admin forms used to save settings, modify contact form configurations, or perform other state-changing actions.
-
Check for nonce verification in plugin codeIf you have file system access, locate the plugin directory (wp-content/plugins/bigcontact). Search PHP files for 'wp_verify_nonce' or 'check_admin_referer' functions, particularly around form handling code that processes admin submissions.Affected if Form processing code lacks nonce verification calls, meaning submitted data is processed without validating the request origin.
You are affected if the BigContact Contact Page plugin version is 1.5.8 or lower AND the plugin is active, as these versions lack proper anti-CSRF token validation on administrative actions.
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 BigContact Contact Page plugin to the latest available version immediately. Additionally, ensure WordPress nonce tokens are properly implemented on all form submissions and state-changing actions within the plugin to prevent future CSRF attacks.
Fix this in Bigcontact Contact Page
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22694 — 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-22694 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