CVE-2024-52395
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 · uneditedMissing Authorization vulnerability in QuantumCloud Floating Buttons for WooCommerce shop-assistant-for-woocommerce-jarvis allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Floating Buttons for WooCommerce: from n/a through <= 2.8.8.
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 confidenceThis is a Missing Authorization (Broken Access Control) vulnerability in the QuantumCloud Floating Buttons for WooCommerce WordPress plugin. The plugin fails to properly verify user permissions before allowing access to certain administrative or sensitive functions, potentially allowing unauthenticated or low-privilege users to perform actions they should not have access to.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Verify the plugin is installedCheck if the Floating Buttons for WooCommerce plugin directory exists in your WordPress installation at wp-content/plugins/ or list installed plugins via WordPress admin under Plugins > Installed PluginsAffected if The plugin appears in the installed plugins list
-
Identify the installed versionIn WordPress admin, go to Plugins > Installed Plugins and find 'Floating Buttons for WooCommerce' - the version number is displayed below the plugin name. Alternatively, check the main plugin file (e.g., floating-buttons-for-woocommerce.php) or readme.txt for the 'Version' headerAffected if A version number is displayed (plugin is installed)
-
Compare version to the fixed releaseCompare the installed version number to 2.8.9. Versions below 2.8.9 (such as 2.8.8, 2.8.7, etc.) are affected. Versions 2.8.9 and above include the authorization fixAffected if The installed version is lower than 2.8.9 (e.g., 2.8.8 or earlier)
-
Confirm vulnerable endpoints are accessible (optional manual check)If the plugin exposes AJAX endpoints or admin URLs, attempt to access them without proper authentication or low-privilege user session to verify the access control gap exists. Use browser developer tools or curl to test GET/POST requests to plugin endpointsAffected if Unauthenticated or subscriber-level users can access admin functions or execute sensitive operations
You are affected if Floating Buttons for WooCommerce plugin is installed with a version lower than 2.8.9, as the missing authorization check allows improper access to sensitive functions.
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.
From vendor dataUpdate the Floating Buttons for WooCommerce plugin to the latest version (2.8.9 or higher) which should include proper authorization checks. If no update is available, restrict access to the plugin's administrative functions via server-side access controls until a patch is released.
- 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-2024-52395 — 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-2024-52395 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