Articles · Security research

CVE-2026-48201: Unauthenticated Stored XSS in Fast Velocity Minify <= 3.5.7

· Alpaslan Fatih Sözer, attorney at law, Denizli Bar Association

Advisory summary. Fast Velocity Minify for WordPress versions <= 3.5.7 contained an unauthenticated Stored Cross-Site Scripting (XSS) vulnerability in its bundled HTML minification parser, tracked as CVE-2026-48201 and fixed in version 3.5.8 (released 28 October 2026).

  • Product: Fast Velocity Minify (WordPress plugin, slug fast-velocity-minify)
  • Affected / Patched: <= 3.5.7 / Fixed in 3.5.8
  • Classification: CWE-79 (Stored Cross-Site Scripting) · CVSS 3.1: 7.1 (High) (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L)
  • Credit: Alpaslan Fatih Sözer (reported via Patchstack Bug Bounty Program)

Fast Velocity Minify buffers rendered WordPress pages and runs them through a bundled copy of simplehtmldom to strip whitespace and comments before serving HTML to visitors. While reviewing plugins that embed this parser in a local isolated test environment in October 2026, I found that version 3.5.7 remained vulnerable to attribute injection through predictable parser placeholders.

Root cause

Before parsing a document, the bundled HTML parser temporarily replaces protected blocks (<script>, <style>, HTML comments, and <code> bodies) with numbered placeholders, then restores them afterward. In version 3.5.7, placeholder keys used a fixed prefix and sequential counter:

// libs/simplehtmldom/simple_html_dom.php (3.5.7)
$key = '___noise___' . sprintf('% 5d', count($this->noise) + 1000);

During attribute parsing, parse_attr() restored any matching placeholder string directly into attribute values without escaping quotes:

// libs/simplehtmldom/simple_html_dom.php (3.5.7), parse_attr()
$value = $this->restore_noise($value);

Two properties combined to create the vulnerability. First, the placeholder format (___noise___ 1000, ___noise___ 1001, ...) was predictable. Second, restoring a stashed block inside a quoted attribute value without escaping allowed a literal quote inside the stashed content to break out of the attribute and inject new HTML attributes.

Trigger mechanism

WordPress allows benign tags such as <abbr title="..."> and <code> in standard comments and sanitizes them on save. If a comment contained a crafted placeholder string inside an <abbr title> attribute followed by a <code> element starting with a quote, the stored comment remained harmless in the database and when the plugin was deactivated. When Fast Velocity Minify processed the page, however, it stashed the <code> body and restored it unescaped inside the title attribute:

<!-- stored comment in database (inert) -->
<abbr title="___noise___ 1038">...</abbr><code>" data-example="</code>

<!-- rewritten HTML output served by plugin 3.5.7 -->
<abbr title="" data-example="">...</abbr>

Because the plugin skips processing for URLs containing a query string (such as ?fvmskip=1), fetching the same page with a dummy query parameter returned the exact pre-parser HTML, allowing the placeholder index to be counted directly without guessing. An invalid index also triggered an infinite loop in the bundled restore_noise() implementation, a known issue noted in the library's own inline comment.

Scope and impact boundaries

  • Preconditions: Default plugin settings were sufficient once activated (no custom option needed). Sites using plain permalinks (/?p=1) were unaffected because the plugin skips query-string URLs. On sites with standard comment moderation, an attacker needed an approved commenter address under WordPress default moderation rules.
  • Target audience: Under default settings, Fast Velocity Minify does not process pages for logged-in users. Injected event-handler attributes therefore executed in the browsers of unauthenticated visitors rather than authenticated administrators.
  • Testing boundary: All reproduction and verification took place exclusively on a local, offline test WordPress installation.

Vendor fix (version 3.5.8)

Version 3.5.8 resolved both root causes and the infinite-loop hazard:

// libs/simplehtmldom/simple_html_dom.php (3.5.8)
try { $rand = bin2hex(random_bytes(8)); } catch (Throwable $e) { $rand = md5(uniqid((string) wp_rand(), true)); }
$this->noise_marker = '___noise_' . $rand . '___';
  • Per-parse random marker: Each parse run generates a random 16-hex-character marker, preventing user content from forging placeholders.
  • Attribute quote escaping: Modified attribute values are escaped in makeup() before serialization so quotes cannot break out of attribute delimiters.
  • Safe restoration loop: Unknown placeholders are removed rather than causing an infinite loop.

Remediation

  • Update Fast Velocity Minify to version 3.5.8 or later.
  • Purge all page caches (including hosting and CDN caches) after updating so previously rewritten HTML is not served from cache.
  • Audit existing comments for unexpected occurrences of ___noise___.

Disclosure timeline

  • 22 October 2026: Vulnerability verified locally and reported to Patchstack; validated and forwarded to the vendor the same day.
  • 28 October 2026: Vendor released Fast Velocity Minify 3.5.8 with the fix and researcher credit.
  • 30 October 2026: CVE-2026-48201 published in the CVE List and Patchstack Vulnerability Database.

For the full Turkish legal and technical commentary (including Turkish Data Protection Law KVKK Art. 12 implications), see the Turkish write-up. For related WordPress security advisories, see CVE-2026-111835 (Swish for WooCommerce) and CVE-2026-110900 (BookIt), or our overview of IT law, cybersecurity and KVKK compliance in Türkiye.

References

Published 21 November 2026 after coordinated disclosure and patch release (3.5.8).