dbcve.org
Floating ButtonWordPress extension · Wow Company

CVE-2023-52149

HIGH · 8.8 CVSS v3.1 Published 2024-01-05
Fix available
A fix is available. Upgrade to after 6.0 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in Wow-Company Floating Button.This issue affects Floating Button: from n/a through 6.0.

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

Cross-Site Request Forgery (CSRF) vulnerability in the Wow-Company Floating Button WordPress plugin (versions up to 6.0) allows attackers to induce authenticated users to perform unintended actions by tricking them into submitting malicious requests.

MitigationImplement anti-CSRF tokens (nonces) on all state-changing actions and validate nonce/s origin headers server-side before processing requests.

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
Floating ButtonWordPress extension
Affected:<= 6.0

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
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 checks

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

  1. Verify plugin is installed
    Check WordPress admin under Plugins > Installed Plugins for 'Wow-Company Floating Button' or inspect /wp-content/plugins/ directory for the floating-button folder
    Affected if Plugin folder exists in the WordPress installation
  2. Determine installed version
    In WordPress admin, click on the plugin to view details and find the version number, or open /wp-content/plugins/floating-button/readme.txt and check the Version: line in the header
    Affected if Version is 6.0 or lower
  3. Confirm plugin is active
    In WordPress admin Plugins list, check if 'Wow-Company Floating Button' shows as 'Active' under the status column
    Affected if Plugin is active and accessible to users
  4. Check for CSRF protection in plugin code
    Inspect plugin PHP files (particularly those handling form submissions or settings changes) and search for wp_nonce_field, wp_verify_nonce, or check_admin_referer function calls on state-changing actions
    Affected if State-changing actions lack nonce verification logic

User is affected if Wow-Company Floating Button plugin is installed, active, and running at version 6.0 or below without proper nonce validation on sensitive actions.

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.

From vendor data
Upgrade available Upgrade to a release after 6.0
Interim mitigation

Implement anti-CSRF tokens (nonces) on all state-changing actions and validate nonce/s origin headers server-side before processing requests.

Fix this in Floating Button Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-52149 — 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-52149 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