CVE-2025-11927 MEDIUM

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

Vendor Gijo
Product Flying Images: Optimize and Lazy Load Images for Faster Page Speed
Weakness CWE-79 · XSS
Published November 1, 2025
Last update April 8, 2026

CVSS base score

4.4/10
Attack vector Network
Attack complexity High
Privileges required High
User interaction None
Confidentiality Low
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N

What the vulnerability does

01Description

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. This makes it possible for authenticated attackers, with administrator-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.

Explanation of Vulnerability in Simple Terms

02Summary

Flying Images versions up to 2.4.14 contain a stored cross-site scripting (XSS) vulnerability. An authenticated administrator with high privileges can inject malicious scripts into the plugin settings. When other users view affected pages, the injected code executes in their browsers, potentially compromising their sessions or stealing data. The vulnerability requires administrator access and specific configuration conditions to exploit.

What an attacker can do

03Attacker Capabilities

Inject malicious JavaScript that executes when other users view the site.

Potential impact on your site

04Site Impact

Compromised user sessions, credential theft, or malware distribution if an admin account is breached.

Conditions required to exploit

05Prerequisites

Administrator account with high privileges; specific attack complexity conditions must be met.

Key dates

06Disclosure timeline

November 1, 2025 CVE published
April 8, 2026 Record updated