The Flying Scripts: Delay JavaScript to Improve Site Speed & Performance plugin for WordPress is…

Why it is Yellow

• CVSS 7.2 high
• Remotely exploitable without logging in

References

• https://plugins.trac.wordpress.org/browser/flying-scripts/tags/1.2.4/html-rewrite.php#L36
• https://plugins.trac.wordpress.org/browser/flying-scripts/tags/1.2.4/html-rewrite.php#L64
• https://plugins.trac.wordpress.org/browser/flying-scripts/tags/1.2.4/lib/dom-parser.php#L2112
• https://plugins.trac.wordpress.org/browser/flying-scripts/tags/1.2.4/lib/dom-parser.php#L2207
• https://plugins.trac.wordpress.org/browser/flying-scripts/tags/1.2.4/lib/dom-parser.php#L2226
• https://plugins.trac.wordpress.org/browser/flying-scripts/tags/1.2.4/lib/dom-parser.php#L497
• https://plugins.trac.wordpress.org/changeset?reponame=&old=3737597%40flying-scripts&new=3737597%40flying-scripts
• https://www.wordfence.com/threat-intel/vulnerabilities/id/0ddc518c-02a0-46a5-93e9-0d92a045b35b?source=cve

Original description

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.