CVE-2026-119175 · Package
NO FIX YET · SEE WHAT TO DO
The Flying Images image optimization and lazy-loading plugin for WordPress does not sanitize the comment field, so an unauthenticated visitor can store a script in a comment. The script runs in the browser of anyone who views the page, including administrators.
first public Nov 7, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Sites running the Flying Images plugin at version 2.4.15 or older where comments are enabled. Exposure is greatest when a first-time commenter is approved once, because later comments from the same name and email then skip moderation. Sites without the plugin or with comments disabled can skip it.
Not affected if comments-disabled, plugin-newer-than-2.4.15, plugin-not-installed
Who cares flying-images, self-hosted, wordpress
wp-content/plugins/ (look for the Flying Images plugin's version header)2.4.15 or olderThe Flying Images: Optimize and Lazy Load Images for Faster Page Speed plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 2.4.15 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. A first-time commenter's submission requires a single administrator approval under the default comment_previously_approved setting; however, once approved, all subsequent comments from the same name and email pair bypass moderation, and the injected script executes for every visitor — including administrators viewing the post from the front end.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.