Void Contact Form 7 Widget For Elementor Page BuilderWordPress extension · Voidcoders
CVE-2022-47166
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 voidCoders Void Contact Form 7 Widget For Elementor Page Builder plugin <= 2.1.1 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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the Void Contact Form 7 Widget For Elementor plugin allows attackers to induce authenticated users to perform unintended actions by tricking them into submitting malicious requests, likely through the plugin's form submission endpoints that lack proper anti-CSRF token validation.
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
Void Contact Form 7 Widget For Elementor Page BuilderWordPress extension
< 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.
-
Verify the Void Contact Form 7 Widget For Elementor plugin is installedNavigate to WordPress admin > Plugins and look for 'Void Contact Form 7 Widget For Elementor' in the installed plugins list, or inspect the plugin directory at wp-content/plugins/void-elementor-contact-form7Affected if The plugin appears in the installed plugins list regardless of activation status
-
Check the installed plugin versionIn WordPress admin > Plugins, find the plugin and view the version number displayed beneath the plugin name, or read the main plugin file header to extract the Version fieldAffected if The version number is lower than 2.2 (for example, 2.1, 2.0, 1.x)
-
Confirm Elementor Page Builder is activeNavigate to WordPress admin > Plugins and verify that Elementor Website Builder is installed and activated, as this plugin is an Elementor widget extensionAffected if Elementor is installed and the Void Contact Form 7 Widget plugin is in use
-
Identify active form widgets using the pluginEdit any page or post with Elementor, open the widget panel, and search for 'Contact Form 7' or 'Void' widgets to see if any form widgets from this plugin are placed on pagesAffected if Form widgets from the Void Contact Form 7 Widget plugin are present on published pages
-
Inspect form submission endpoint for CSRF protectionUse browser developer tools > Network tab, submit a form using the plugin, and inspect the request headers and form data for a nonce token (wpnonce, _wpnonce, or similar) or check if the plugin admin settings reveal CSRF token configurationAffected if The form submission request contains no anti-CSRF token parameter and the plugin version is below 2.2
A user is affected if the Void Contact Form 7 Widget For Elementor plugin version is below 2.2 and the plugin is installed and active with form widgets in use on the site.
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 · scoped2.2
Implement anti-CSRF tokens (nonces) on all form actions and validate the Origin/Referer headers to ensure requests originate from legitimate sources; update to plugin version 2.1.2 or later if available.
version 2.2
- Update the Void Contact Form 7 Widget For Elementor Page Builder plugin to version 2.2 or later through the WordPress plugin dashboard or via wp-cli: wp plugin update void-contact-form-7-widget-for-elementor
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Void Contact Form 7 Widget For Elementor Page Builder
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47166 — 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-2022-47166 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