CVSS VectorNVD
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Lifecycle Timeline
2DescriptionNVD
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.
AnalysisAI
Stored Cross-Site Scripting in Taeggie Feed plugin for WordPress (all versions up to 0.1.10) allows authenticated attackers with contributor-level access or above to inject arbitrary JavaScript via the taeggie-feed shortcode's name attribute, which is rendered unsanitized in both a script tag ID and jQuery.getScript() call. The vulnerability has a CVSS score of 6.4 with cross-site impact; no public exploit code or active exploitation has been confirmed at this time.
Technical ContextAI
The vulnerability exists in the plugin's render() method, which processes the name attribute from the [taeggie-feed] shortcode and directly concatenates it into HTML without proper escaping or sanitization. Specifically, the unsanitized name parameter is injected into two dangerous contexts: the id attribute of a <script> tag and as a parameter to jQuery.getScript(). This is a classic Stored XSS vulnerability (CWE-79: Improper Neutralization of Input During Web Page Generation) where the malicious payload persists in the WordPress database as part of the page or post content and executes in the browser context of any user who views the affected page. The vulnerability requires authentication at the contributor level or higher, meaning only registered WordPress users with publication permissions can exploit it, but the resulting XSS payload executes for all site visitors including administrators and other users.
Affected ProductsAI
The Taeggie Feed plugin for WordPress is affected in all versions up to and including 0.1.10. The plugin is hosted on the official WordPress plugin repository at wordpress.org/plugins/taeggie-feed/. No specific CPE string is provided in the intelligence sources; however, affected installations include any WordPress site running Taeggie Feed version 0.1.10 or earlier. The vulnerability was confirmed and disclosed by Wordfence security research team.
RemediationAI
The primary remediation is to update the Taeggie Feed plugin to a patched version beyond 0.1.10. WordPress administrators should navigate to Plugins > Installed Plugins in the WordPress dashboard, locate Taeggie Feed, and apply any available update. If no patched version has been released by the plugin developers, administrators should consider disabling or removing the Taeggie Feed plugin until a fix is available. As an interim workaround, site administrators can restrict the contributor role permissions to users who are fully trusted, or audit existing posts and pages using the [taeggie-feed] shortcode for suspicious name attributes. The plugin's source code is available at https://plugins.trac.wordpress.org/browser/taeggie-feed/trunk/taeggie_feed.php and patch details may be reviewed at https://plugins.trac.wordpress.org/changeset/3336357/. For detailed vulnerability information and remediation guidance, consult the Wordfence threat intelligence report at https://www.wordfence.com/threat-intel/vulnerabilities/id/c7f5ac78-5195-4b59-abc7-f41e487f9361.
Share
External POC / Exploit Code
Leaving vuln.today