WordPress Flying Images plugin <= 2.4.15 - Cross Site Scripting (XSS) vulnerability
Affects the Flying Images WordPress plugin version 2.4.15 and earlier, by Gijo Varghese. Fixed in 2.4.16.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.4.16
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Flying Images plugin version 2.4.15 or earlier
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 19/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
The Flying Images plugin for WordPress has a stored cross-site scripting flaw that lets an attacker inject malicious scripts into web pages. It can be reached remotely without logging in, but a user must take some action before the script runs.
Read the original description
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Gijo Varghese Flying Images nazy-load allows Stored XSS.This issue affects Flying Images: from n/a through 2.4.15.
cve.now Index
- Exploitation0/40No signal
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 69 if added to CISA KEV
- Would score about 64 if CISA's SSVC rates exploitation active
What to do
Check whether your setup matches what the bug needs.
Flying Images plugin version 2.4.15 or earlierUpgrade to a fixed version: 2.4.16.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- nazy-load
through 2.4.15
Evidence 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-121780
Is CVE-2026-121780 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The plugin fails to properly sanitize input, which lets an attacker inject malicious scripts into pages of the site. Visitors' browsers can then run those scripts, which may steal visitor data or hijack accounts.Source: patchstack.com
Which versions are affected by CVE-2026-121780?
nazy-load: through 2.4.15.Source: cve.now feed data
Am I affected, and how do I check?
Flying Images plugin version 2.4.15 and earlier are affected. To check, look at the installed plugin version in the WordPress admin Plugins page.Source: patchstack.com
How do I fix CVE-2026-121780?
Update the Flying Images plugin to version 2.4.16 or later.Source: patchstack.com