CVE-2025-6382
BaseFortify
Publication date: 2025-07-24
Last updated on: 2026-04-08
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| taeggie | taeggie_feed | 0.1.10 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability in the Taeggie Feed WordPress plugin is a Stored Cross-Site Scripting (XSS) issue. It occurs because the plugin's render() method takes user-supplied input from the 'name' attribute of its shortcode and injects it directly into a <script> tag without proper escaping. This allows authenticated users with contributor-level access or higher to inject arbitrary JavaScript code that executes whenever any user views the affected page.
How can this vulnerability impact me? :
This vulnerability can allow attackers with contributor-level access to inject malicious scripts into web pages. These scripts can execute in the browsers of users who visit the infected pages, potentially leading to theft of user credentials, session hijacking, defacement, or other malicious actions that compromise the security and integrity of the website and its users.
What immediate steps should I take to mitigate this vulnerability?
Since the Taeggie Feed plugin version 0.1.10 and earlier are vulnerable and the plugin has been closed and is unavailable for download pending a full security review, the immediate mitigation step is to deactivate and remove the Taeggie Feed plugin from your WordPress installation until a secure version is released. [1]