Plugins · blog-floating-button · data as of 2026-11-04
Is Blog Floating Button safe? Known vulnerabilities and latest version
- Latest version
- 1.4.21
- Last updated
- 2026-07-31
- Active installs
- 8,000+
- Known issues on record
- 3
- Unpatched in latest
- 0
- Tested up to WP
- 7.0.8 · PHP 8.2+
Blog Floating Button (BFB) adds customizable floating buttons to your WordPress site and directs visitors to key landing pages. — by 1meril
What to do
- Update to the latest version (1.4.21). Anything older than 1.4.21 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.
With WP-CLI: wp plugin get blog-floating-button --field=version shows what you run; wp plugin update blog-floating-button updates it.
Check your version
Known vulnerabilities
3 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.
high 7.1 CVE-2026-28170 · published 2026-08-13
Cross-site scripting (XSS) in Blog Floating Button (1.4.20 and older)
- Affected
- 1.4.20 and older
- Fixed in
- 1.4.21
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Unauthenticated Cross Site Scripting (XSS) in Blog Floating Button <= 1.4.20 versions.
medium 6.1 CVE-2026-15383 · published 2026-08-03
Cross-site scripting (XSS) in Blog Floating Button (1.4.20 and older)
- Affected
- 1.4.20 and older
- Fixed in
- 1.4.21 *
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by CISA ADP
Details from the advisory
The Blog Floating Button WordPress plugin through 1.4.20 does not sanitize or escape the visitor User-Agent header, which it stores through an unauthenticated tracking REST endpoint and later renders unescaped in an administrator report page. This allows an unauthenticated attacker to store a malicious script that executes in the session of any administrator who views the access report, leading to site takeover.
high 8.8 CVE-2023-27445 · published 2023-11-13
Cross-site request forgery (CSRF) in Blog Floating Button (1.4.12 and older)
- Affected
- 1.4.12 and older
- Fixed in
- 1.4.13
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
Cross-Site Request Forgery (CSRF) vulnerability in Meril Inc. Blog Floating Button plugin <= 1.4.12 versions.
Recent activity
- 2026-07-31 — latest release on wordpress.org (1.4.21).
- 2026-08-13 — Cross-site scripting (XSS) disclosed (CVE-2026-28170), fixed in 1.4.21.
- 2026-08-03 — Cross-site scripting (XSS) disclosed (CVE-2026-15383), fixed in 1.4.21.
- 2023-11-13 — Cross-site request forgery (CSRF) disclosed (CVE-2023-27445), fixed in 1.4.13.
Get an email when Blog Floating Button has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Blog Floating Button (blog-floating-button) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
Types found in this plugin: Cross-site scripting (XSS) (2) · Cross-site request forgery (CSRF) (1)
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/blog-floating-button (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/blog-floating-button"><img src="https://laskyr.com/plugins/blog-floating-button/badge.svg" alt="Blog Floating Button vulnerability status"></a>