CVE-2023-23984
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 Wow-Company Bubble Menu – circle floating menu plugin <= 3.0.1 leading to form deletion.
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 confidenceA CSRF vulnerability in the Wow-Company Bubble Menu WordPress plugin (versions 3.0.1 and below) allows remote attackers to trick authenticated administrators into unknowingly submitting requests that delete forms, due to missing anti-CSRF token validation on the form deletion action.
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< 3.0.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
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
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 if Wow Company Bubble Menu plugin is installedNavigate to WordPress admin dashboard under Plugins > Installed Plugins and look for 'Bubble Menu' by Wow Company, or inspect the wp-content/plugins/ directory for a bubble-menu folderAffected if The plugin is present in the WordPress installation
-
Verify the installed versionIn Plugins > Installed Plugins, click on the plugin details link for Bubble Menu and check the version number, or read the version from the plugin's main PHP file or readme.txt in wp-content/plugins/bubble-menu/Affected if The version is 3.0.1 or below (any version < 3.0.2)
-
Identify form deletion functionalityLocate the plugin's admin interface or any form management section where forms can be deleted. Check the plugin's PHP files (particularly admin files) for any delete or remove action handlers related to formsAffected if The plugin has a form deletion feature that can be accessed via the WordPress admin dashboard
-
Verify absence of nonce token validation on delete actionInspect the plugin's PHP code handling the form deletion action. Look for wp_verify_nonce, check_admin_referer, or nonce_field function calls in the delete handler. If these are missing, the plugin is vulnerableAffected if The form deletion action lacks nonce verification (no wp_verify_nonce, check_admin_referer, or similar CSRF protection in the delete handler)
The environment is affected if the Wow Company Bubble Menu plugin version 3.0.1 or below is installed and the form deletion action lacks proper nonce token validation.
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 · scoped3.0.2
Implement nonce token validation on all state-changing operations (including form deletion) and verify the nonce on the server side before executing the delete action. Additionally, configure SameSite attributes on session cookies.
Bubble Menu plugin version 3.0.2
- 1. Backup your WordPress site before making any changes.
- 2. Navigate to the WordPress admin dashboard.
- 3. Go to Plugins > Installed Plugins.
- 4. Locate the 'Bubble Menu – circle floating menu' plugin by Wow-Company.
- 5. Check the current version number to confirm it is below 3.0.2.
- 6. If an update is available, click 'Update Now' to upgrade to version 3.0.2 or higher.
- 7. Alternatively, navigate to Dashboard > Updates and update the plugin from there.
- 8. After updating, verify the plugin is running version 3.0.2 or later.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-23984 — 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-23984 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