Live › vulnerability › CVE-2026-109990
Go to dashboardThe Flying Scripts WordPress plugin up to and including 1.2.4 fails to sanitize the 'comment' parameter, letting unauthenticated attackers store script in pages. The script runs in the browser of anyone who opens an injected page, which can include administrators.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Sites running the Flying Scripts plugin at version 1.2.4 or earlier, where the plugin's output rewriting is active on public pages. Sites that do not have the plugin installed are not affected. Whether comment submission is open to anonymous visitors on a given site is unknown from the sources.
No product ranges from the sources yet.
wp plugin get flying-scripts --field=version1.2.4 as affected1.2.4; the exact fixed version is unknown from the sourcesEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
The Flying Scripts: Delay JavaScript to Improve Site Speed & Performance plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 1.2.4 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The exploit bypasses WordPress core's save-time kses sanitization entirely because the payload uses only kses-allowed elements — an <abbr title> attribute and <code> text content — and the XSS is introduced post-save when the plugin's output-buffer rewriter substitutes a double-quote-bearing <code> body into the <abbr title> attribute via predictable, unsalted noise placeholder keys.
This page as .md · .json · in your agent: get_signal("CVE-2026-109990")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.