Cf7 Invisible RecaptchaWordPress extension · Vsourz
CVE-2023-28167
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 Vsourz Digital CF7 Invisible reCAPTCHA plugin <= 1.3.3 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 Vsourz Digital CF7 Invisible reCAPTCHA plugin versions 1.3.3 and below allows attackers to trick authenticated users into performing unintended actions by forcing their browser to send malicious requests, as the plugin lacks proper CSRF token validation on form submissions.
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
Cf7 Invisible RecaptchaWordPress extension
<= 1.3.3CVSS 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 plugin versionAccess WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate 'Vsourz Cf7 Invisible Recaptcha' and verify the version number displayedAffected if The version listed is 1.3.3 or lower
-
Inspect form source for nonce fieldView the source HTML of any form protected by this plugin (typically Contact Form 7 forms), look for a hidden input field containing a nonce token (usually named '_wpnonce' or similar) within the form tagsAffected if No hidden nonce token field is present in the form HTML
-
Check plugin PHP code for nonce validationAccess the plugin directory via file manager or FTP, locate the main plugin PHP file handling form submissions, search for 'wp_verify_nonce' or 'wp_nonce_field' function calls to verify CSRF protection existsAffected if No nonce validation functions are found in form handling code
You are affected if the installed plugin version is 1.3.3 or lower AND forms lack hidden nonce token fields in HTML AND the plugin code contains no nonce validation logic.
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 · scopedImplement anti-CSRF tokens (nonces) on all form submissions and validate these tokens server-side before processing any requests to prevent unauthorized actions.
Latest version available in WordPress plugin repository (version higher than 1.3.3)
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find 'CF7 Invisible reCAPTCHA' by Vsourz Digital
- Check the current version installed
- If version is 1.3.3 or lower, click 'Update Now' to install the latest version
- Alternatively, navigate to Plugins > Add New > Upload to manually upload the updated plugin zip file from the WordPress plugin repository
- After updating, verify the plugin is functioning correctly with contact forms
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Cf7 Invisible Recaptcha
Scoped from the published advisory
- Consultation2.0 h
- Implementation6.0 h
- Testing3.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 $3,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28167 — 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-28167 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