What this page helps you verify fast
This hub clusters every indexed record for Floating Action Button so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.
Review known vulnerability records for the WordPress plugin Floating Action Button (`floating-action-button`), including severity, CVE references, affected versions, and patch status.
Recent tracked CVEs on this page include CVE-2023-31088, so operators can jump from disclosure to patch validation without scanning the full feed first.
Start with the highest-signal CVE records for this WordPress plugin before scanning the full vulnerability feed.
This hub clusters every indexed record for Floating Action Button so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.
These recent records surface the CVE strings, patch cues, and direct report links most operators need first.
The Floating Action Button plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.2.1. This is due to missing or incorrect nonce validation...
The Floating Action Button plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including,
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_f...
Sorted by latest disclosure date so newly published issues surface first.
The Floating Action Button plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.2.1. This is due to missing or incorrect nonce validation on the wp_ajax_fz_fab_settings_save function. This makes it possible for unauthenticated a...
The Floating Action Button plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including,
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)....