WPEMATICO RSS FEED FETCHER · CVE-2026-120573 · Package
NO FIX YET
The WPeMatico RSS Feed Fetcher WordPress plugin up to and including 2.9.1 does not sanitize the post_category parameter. An authenticated contributor can store a script that runs in the browser of any editor or administrator who opens the WPeMatico campaigns list.
first public Nov 13, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Sites running the WPeMatico RSS Feed Fetcher plugin at version 2.9.1 or earlier where contributors or higher can create content. The attacker needs a contributor-level account, and the payload fires for users with edit_posts, including administrators who open the campaigns screen. Sites without the plugin, or with it updated past the affected range, can skip it.
Not affected if no-contributor-accounts, plugin-not-installed
Who cares self-hosted, wordpress, wpematico
2.9.1 and earlier are affected.campaign_data for unexpected script content.No fix yet, per the sources.
The WPeMatico RSS Feed Fetcher plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'post_category' parameter in all versions up to, and including, 2.9.1 due to insufficient input sanitization and output 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. The injected payload is persisted in post meta as campaign_data, bypassing wp_kses sanitization, and executes in the browser session of any user with edit_posts — including Administrators — who opens the WPeMatico campaigns list screen.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.