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.
Published: 2026-08-03
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

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. Given the lack of an official patch yet, the risk remains high for any site running the affected plugin version.

Generated by OpenCVE AI on August 3, 2026 at 08:39 UTC.

Remediation

No vendor fix or workaround currently provided.

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 3, 2026 at 08:39 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 03 Aug 2026 06:45:00 +0000

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

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: WPScan

Published:

Updated: 2026-08-03T06:00:12.685Z

Reserved: 2026-07-10T09:42:57.466Z

Link: CVE-2026-15383

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-03T08:45:03Z

Weaknesses

No weakness.