Floating Action Button <= 1.2 - Missing Authorization
Strategic Overview
- Status
- Patched in 1.2.1
- Affected Plugin
- Floating Action Button
- Affected Version
<= 1.2- CVSS
- 7.3High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE pending
At a glance
This record tracks a high-severity Missing Authorization vulnerability in the Floating Action Button WordPress plugin, affecting versions <= 1.2. It carries a CVSS score of 7.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.2.1; sites on affected versions should update now. Disclosed August 2022.
Vulnerability Overview
The Floating Action Button plugin for WordPress is vulnerable to authorization bypass in versions up to, and including, 1.2 due to a missing capability check and nonce validation on the fz_fab_settings_save() function that is called via an AJAX action (including a nopriv action). This makes it possible for unauthenticated attackers to modify the plugin's settings.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-862: Missing Authorization
Floating Action Button <= 1.2 carries this weakness at fz_fab_settings_save(), and reaching it takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Floating Action Button the fix is 1.2.1: builds <= 1.2 are affected, anything from 1.2.1 onward is not.
Remediation
Update to version 1.2.1, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Floating Action Button 1.2.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Floating Action Button
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C