CVE-2025-6382 Taeggie Feed <= 0.1.10 - Authenticated (Contributor+) Stored Cross-Site Scripting via name Attribute
Authenticated attackers can inject arbitrary scripts via the name attribute in the Taeggie Feed plugin, leading to stored XSS execution.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2025-6382?
CVE-2025-6382 is a medium-severity cross-site scripting vulnerability in Taeggie Feed, published on 24 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
The Taeggie Feed plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's taeggie-feed shortcode in all versions up to, and including, 0.1.10. The plugin’s render() method takes the user-supplied name attribute and injects it directly into a <script> tag - both in the id attribute and inside jQuery.getScript() - without proper escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
Weakness: CWE-79
Which versions are affected by CVE-2025-6382?
How do I fix CVE-2025-6382?
No fix has been published for CVE-2025-6382 yet. Limit exposure of the affected software until one is available.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2025-6382 being exploited?
There is no known exploitation of CVE-2025-6382 in the wild and no public exploit code.
Sources
Also known as GHSA-rv4p-hv2v-9w74.