gijo vulnerabilities (CVE)

CVE records published for gijo, newest first. Follow to get an email when a new one appears.

4 results
6.4Medium
CVE-2026-125012

Flying Images: Optimize and Lazy Load Images for Faster Page Speed <= 2.4.16 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'post_content' Parameter

gijo Flying Images: Optimize and Lazy Load Images for Faster Page Speed

The Flying Images: Optimize and Lazy Load Images for Faster Page Speed plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'post_content' parameter in all versions up to, and including, 2.4.16 due to insufficient input sanitization and o…

7.2High
CVE-2026-119175

Flying Images: Optimize and Lazy Load Images for Faster Page Speed <= 2.4.15 - Unauthenticated Stored Cross-Site Scripting via Comment Content

gijo Flying Images: Optimize and Lazy Load Images for Faster Page Speed

The 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…

7.2High
CVE-2026-109990

Flying Scripts: Delay JavaScript to Improve Site Speed & Performance <= 1.2.4 - Unauthenticated Stored Cross-Site Scripting via Comment Content

gijo Flying Scripts: Delay JavaScript to Improve Site Speed & Performance

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 outpu…

4.4Medium
CVE-2025-11927

Flying Images: Optimize and Lazy Load Images for Faster Page Speed <= 2.4.14 - Authenticated (Admin+) Stored Cross-Site Scripting

gijo Flying Images: Optimize and Lazy Load Images for Faster Page Speed

The Flying Images: Optimize and Lazy Load Images for Faster Page Speed plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 2.4.14 due to insufficient input sanitization and output escaping…