dbcve.org
Void Contact Form 7 Widget For Elementor Page BuilderWordPress extension · Voidcoders

CVE-2023-52214

HIGH · 8.8 CVSS v3.1 Published 2024-03-26
Fix available
A fix is available. Upgrade to 2.4 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Missing Authorization vulnerability in voidCoders Void Contact Form 7 Widget For Elementor Page Builder.This issue affects Void Contact Form 7 Widget For Elementor Page Builder: from n/a through 2.3.

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 confidence

Missing authorization vulnerability in the Void Contact Form 7 Widget For Elementor plugin allows authenticated users to access or modify functionality they should not have access to. The CVSS 8.8 score indicates authenticated low-privilege users can likely perform administrative or other users' form-related actions without proper capability checks.

MitigationUpgrade to version 2.3 or later which contains the authorization fix. Until then, restrict user access and monitor for suspicious form-related activity.

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
Affected:< 2.4

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify the plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and search for 'Void Contact Form 7 Widget For Elementor' or check your wp-content/plugins directory for folders containing 'void' and 'elementor' in the name
    Affected if The plugin appears in the list of installed plugins and is activated
  2. Identify the installed version
    In WordPress admin, go to Plugins > Installed Plugins, find the Void Contact Form 7 Widget For Elementor plugin, and note the version number displayed below the plugin name
    Affected if The displayed version number is lower than 2.4 (for example, 2.3, 2.2, 1.x, etc.)
  3. Confirm authenticated user access exists
    In WordPress admin, go to Users > All Users and review the list of registered users. Check if any users exist with roles other than Administrator (such as Editor, Author, Contributor, or Subscriber)
    Affected if There are one or more non-Administrator users with accounts on the site who can log in
  4. Check for unauthorized form actions (optional)
    Review Contact Form 7 entries and any form-related logs for submissions or modifications that do not correspond to Administrator activity or known workflows
    Affected if Form submissions or modifications exist that were created by users without Administrator privileges

Your environment is affected if the Void Contact Form 7 Widget For Elementor plugin is installed with a version lower than 2.4 and your site has any authenticated non-Administrator users who could potentially exploit the missing authorization checks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.4 or later
Fixed in 2.4
Interim mitigation

Upgrade to version 2.3 or later which contains the authorization fix. Until then, restrict user access and monitor for suspicious form-related activity.

Recommended fix High confidence

2.4

  1. Backup your WordPress site before performing any updates
  2. Update Void Contact Form 7 Widget For Elementor Page Builder to version 2.4 or later through the WordPress plugin repository or your plugin management system
  3. Verify the plugin version has been updated to 2.4 or higher in the installed plugins list
  4. Test the contact form functionality to ensure the plugin is functioning correctly after the update

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
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-52214 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-52214 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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