Quick answers
- Is CVE-2026-32569 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-32569 being exploited in the wild.
- How severe is CVE-2026-32569?
- High severity, with a CVSS score of 7.1, published 6 October 2026.
- Which products and versions are affected?
- WP Media folder <= 6.2.2.
- Is there a fix for CVE-2026-32569?
- No fixed version is recorded yet. Patchstack has issued a mitigation rule to block attack attempts until an official patch becomes available; apply this rule immediately through your security provider.</anigation> </invoke> If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-32569 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-32569?
- Check whether you run WP Media folder at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
Patchstack has issued a mitigation rule to block attack attempts until an official patch becomes available; apply this rule immediately through your security provider.</anigation> </invoke>
Technical details
The vulnerability is a reflected or stored cross-site scripting (XSS) flaw in WP Media folder versions 6.2.2 and earlier that requires no authentication to exploit. Attack vectors likely include user interaction (clicking a malicious link), and successful exploitation allows arbitrary JavaScript execution in visitor browsers within the context of the vulnerable site.
Affected products
- WP Media WP Media folder <= 6.2.2
Timeline
- 2026-10-04: disclosed
- 2026-10-06: advisory