CVE-2023-52214 is a medium severity (4.3) missing authorization flaw in the Void Contact Form 7 Widget for Elementor Page Builder WordPress plugin, affecting version 2.3 and earlier. The developer fixed it in version 2.4. Update the plugin to 2.4 or later, and if you cannot update, deactivate it until you can.
What's affected
The NVD record names voidCoders and the Void Contact Form 7 Widget for Elementor Page Builder plugin for WordPress, from the earliest release through 2.3. Patchstack lists 2.4 as the patched version. Upgrade to 2.4 or any later release.
The weakness is CWE-862, missing authorization. The record's CVSS vector is CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N, which gives 4.3 (Medium).
Patchstack lists the required privilege as subscriber. A subscriber is the lowest logged in role on most sites, so anyone who can register an account may qualify. Patchstack rates the priority as low and says the threat is not impactful, while NVD scores it 4.3.
How to check if you're exposed
Start with the plugin list. On a server with WP-CLI, run this from the site folder:
wp plugin list
wp plugin get cf7-widget-elementor
The first command shows every installed plugin with its version and status. The second shows the details of this one. If the slug is not found, the plugin is not installed under that folder name.
Without shell access, open Plugins, Installed Plugins in the admin and read the version under the plugin name. On WordPress multisite, check the network plugin list and each site, since a plugin can be active on only some of them.
A version at or below 2.3 is in the affected range. An inactive plugin is lower risk than an active one, but it is still on disk, so remove it if it is unused.
What to do now
- Open the Plugins screen, or run the WP-CLI check above, and note the installed version.
- Update Void Contact Form 7 Widget for Elementor Page Builder to 2.4 or later on staging first if you test changes, then on production.
- If the update cannot go out today, deactivate the plugin. A deactivated plugin does not run its code.
- Review recent activity: look at user accounts created recently, especially subscribers, and at any changes to contact form settings.
- Add the plugin to whatever tracks your WordPress inventory, so the next advisory finds it quickly.
Why it matters
Missing authorization means the plugin runs an action without first confirming that the person asking is allowed to. The code does the work, but the permission check is absent or too weak. It is a common bug in WordPress plugins, where handlers exposed through the admin or the REST and AJAX interfaces need an explicit capability check.
The impact depends on what the unprotected action does. Here the record rates confidentiality and integrity as indicated by the vector, and Patchstack classes it as broken access control, the first item in the OWASP Top 10. Here the impact is limited to a low confidentiality effect. This CVE is not listed in the CISA Known Exploited Vulnerabilities catalog, and the sources I read do not report exploitation in the wild. Safeguard's free in-browser dependency scan at gold.safeguard.sh/scan and the Gold directory help you track which components you run and which advisories apply.
Quick check
Do I need to be an administrator to trigger CVE-2023-52214?
No. Patchstack lists the required privilege as subscriber, the lowest logged in role. That is why sites that allow open registration should treat it as more exposed.
Is there a patched version?
Yes. Patchstack lists 2.4 as the patched release for versions up to 2.3. Check the plugin's own changelog before you upgrade.
Sources
Last reviewed: 19 October 2026.
