CVE-2026-15383

Blog Floating Button <= 1.4.20 - Unauthenticated Stored XSS via User-Agent Header

Published Aug 3, 2026 CVSS 3.1 · 6.1 Medium EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

This vulnerability arises from the Blog Floating Button WordPress plugin storing the visitor User‑Agent header without proper sanitization. The unsanitized input is later rendered unescaped in an administrator‑only report page, allowing an attacker to inject arbitrary JavaScript. When an administrator views the report, the malicious script runs in their browser session, enabling credential theft or full site compromise. The weakness is a classic Stored Cross‑Site Scripting flaw (CWE‑79).

Affected Systems

WordPress installations using the Blog Floating Button plugin version 1.4.20 or earlier are affected. Administrators with access to the plugin’s access report page are the direct target. The issue is present on any server that actively runs this plugin version and exposes the REST endpoint used for tracking.

Risk and Exploitability

The exploit is simple: craft a malicious User‑Agent header, send it to the tracking endpoint, then coerce an administrator into opening the access report page, where the injected script will execute in their administrator session. The CVSS score of 6.1 indicates a medium severity, and the EPSS score of <1% suggests a low probability of exploitation at this time. Given the lack of an official patch yet, the risk remains high for any site running the affected plugin version.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the Blog Floating Button plugin to the latest available version (at least 1.4.21) or remove the plugin entirely if no newer version addresses the flaw.
  • If an upgrade is not immediately possible, block or strip the User‑Agent header at the web server or reverse‑proxy level before it reaches WordPress, thereby preventing the payload from being stored.
  • Implement a Content Security Policy that disallows inline scripts and restricts script sources to trusted origins, reducing the impact if an injected script does reach the administrator interface.
  • Contact the plugin maintainers to confirm a fix has been released and verify the fix via the CVE reference provided.

Generated by OpenCVE AI on August 4, 2026 at 10:38 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Wordpress-extensions
Wordpress-extensions blog Floating Button
Vendors & Products Wordpress-extensions
Wordpress-extensions blog Floating Button
Type Values Removed Values Added
Weaknesses CWE-79
Metrics cvssV3_1

{'score': 6.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Title Blog Floating Button <= 1.4.20 - Unauthenticated Stored XSS via User-Agent Header
References
Weaknesses
  • CWE-79

    Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Sources

Status
PUBLISHED
Assigner
WPScan
Published
Updated
Aug 3, 2026, 5:05 PM
Reserved
Jul 10, 2026, 9:42 AM
Status
Deferred
Published
Aug 3, 2026, 7:16 AM
Modified
Aug 26, 2026, 4:31 PM