CVE-2024-56238
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 Action Buttons floating-action-buttons allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Floating Action Buttons: from n/a through <= 0.9.1.
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 confidenceThe QuantumCloud Floating Action Buttons WordPress plugin (version <= 0.9.1) contains a missing authorization vulnerability where certain functionality is not properly constrained by access control lists (ACLs). This allows unauthenticated or lower-privileged users to access administrative functions they should not have permission to use.
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.
-
Confirm Floating Action Buttons plugin is installedNavigate to WordPress Admin > Plugins and look for 'Floating Action Buttons' by QuantumCloud, or inspect the plugin directory /wp-content/plugins/floating-action-buttons/ for the main plugin fileAffected if The plugin is installed and active in WordPress
-
Identify the installed plugin versionCheck the plugin header in floating-action-buttons.php for 'Version: x.x.x', or view the plugin details in WordPress Admin > Plugins > Installed PluginsAffected if Version is 0.9.1 or lower (the vulnerable version range)
-
Verify the vulnerability is present by code inspectionExamine the plugin's AJAX handlers (usually in ajax.php or within the main file) and admin functions for missing current_user_can() capability checks before executing sensitive operationsAffected if No capability checks (like current_user_can()) are found before administrative actions, indicating missing authorization controls
-
Test for unauthenticated access to admin functionsIf accessible, attempt to call AJAX endpoints or admin actions without authentication or with a low-privilege user account to confirm they execute without authorization errorsAffected if Administrative functions execute successfully without proper authentication or capability verification
If the Floating Action Buttons plugin version is 0.9.1 or lower AND the code lacks current_user_can() checks before admin functions, the environment is affected by this missing authorization vulnerability.
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 to the latest version of the Floating Action Buttons plugin which includes proper capability checks and authorization controls. If no update is available, manually add current_user_can() checks and nonce verification to all AJAX handlers and admin functions.
- 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-56238 — 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-56238 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