{"id":"CVE-2026-110252","revision":"6a80292d8e21463ea5018d85d5dccde1","records":[{"revision":"6a80292d8e21463ea5018d85d5dccde1","observedAt":"2026-10-23T15:48:27.903+00:00","statement":{"source":"cve-program","id":"CVE-2026-110252","aliases":[],"title":"WPeMatico RSS Feed Fetcher <= 2.9 - Unauthenticated Stored Cross-Site Scripting via RSS Feed Content Import","description":"The WPeMatico RSS Feed Fetcher plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 2.9 This is due to the plugin removing WordPress's wp_filter_post_kses filter from content_save_pre immediately before calling wp_insert_post() with RSS feed content, whenever the campaign's last editor had the unfiltered_html capability — a flag the plugin sets automatically for every admin-saved campaign. Imported item content is taken raw from $item->get_content(), only entity-decoded, and stored verbatim in post_content. This makes it possible for unauthenticated attackers, who publish or compromise an RSS feed that an administrator has subscribed a WPeMatico campaign to, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected imported post.","state":0,"publishedAt":"2026-10-16T06:41:06.918+00:00","modifiedAt":"2026-10-16T14:39:02.268+00:00","affected":[{"ecosystem":"Vendor product","name":"WPeMatico RSS Feed Fetcher","ranges":[],"versions":[],"rawVersionEvidence":"{\n                    \"vendor\": \"etruel\",\n                    \"product\": \"WPeMatico RSS Feed Fetcher\",\n                    \"versions\": [\n                        {\n                            \"version\": \"0\",\n                            \"status\": \"affected\",\n                            \"lessThanOrEqual\": \"2.9\",\n                            \"versionType\": \"semver\"\n                        }\n                    ],\n                    \"defaultStatus\": \"unaffected\"\n                }"}],"metrics":[{"system":"CVSS 3.1","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N","score":5.4,"severity":"MEDIUM"}],"references":["https://www.wordfence.com/threat-intel/vulnerabilities/id/e87fc1bf-af05-4089-a164-8a2e73c68e8c?source=cve","https://plugins.trac.wordpress.org/browser/wpematico/tags/2.9/includes/campaign_fetch.php#L400","https://plugins.trac.wordpress.org/browser/wpematico/tags/2.9/includes/wpematico_functions.php#L3226","https://plugins.trac.wordpress.org/browser/wpematico/tags/2.9/includes/campaign_fetch.php#L777","https://plugins.trac.wordpress.org/browser/wpematico/tags/2.9/includes/campaign_fetch.php#L773","https://plugins.trac.wordpress.org/browser/wpematico/tags/2.9/includes/wpematico_functions.php#L3326","https://github.com/etruel/wpematico/commit/44c4894a0ad92a711c534ad4d822c0b5d7c3dffe","https://plugins.trac.wordpress.org/changeset/3747465/wpematico/trunk/includes/campaign_fetch.php"],"sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-110252","license":"CVE Program Terms of Use","key":"cve-program:CVE-2026-110252","identifiers":["CVE-2026-110252"]},"retained":false,"historicalAffected":[]}],"coverage":[]}