CVE-2026-110252WPeMatico RSS Feed Fetcher <= 2.9 - Unauthenticated Stored Cross-Site Scripting via RSS Feed Content Import
- 5.4MediumCVSS base score
- 0.29%Exploitation in 30 daysEPSS · top 78% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Wordfence
- 3 days later
· 3 days later
Published
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| WordfenceCNA (assigner) | 3.1 | Medium5.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N |
| NVDNVD · Deferred | 3.1 | Medium5.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N |
- EPSS (exploitation in 30 days)
- 0.29% · top 78% of all CVEs (12 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.4.
Affected products
etruel · WPeMatico RSS Feed Fetcher
- affected ≤ 2.9
References
References8
- https://www.wordfence.com/threat-intel/vulnerabilities/id/e87fc1bf-af05-4089-a164-8a2e73c68e8c?source=cve (opens in a new tab)
- https://plugins.trac.wordpress.org/browser/wpematico/tags/2.9/includes/campaign_fetch.php#L400 (opens in a new tab)
- https://plugins.trac.wordpress.org/browser/wpematico/tags/2.9/includes/wpematico_functions.php#L3226 (opens in a new tab)
- https://plugins.trac.wordpress.org/browser/wpematico/tags/2.9/includes/campaign_fetch.php#L777 (opens in a new tab)
- https://plugins.trac.wordpress.org/browser/wpematico/tags/2.9/includes/campaign_fetch.php#L773 (opens in a new tab)
- https://plugins.trac.wordpress.org/browser/wpematico/tags/2.9/includes/wpematico_functions.php#L3326 (opens in a new tab)
- https://github.com/etruel/wpematico/commit/44c4894a0ad92a711c534ad4d822c0b5d7c3dffe (opens in a new tab)
- https://plugins.trac.wordpress.org/changeset/3747465/wpematico/trunk/includes/campaign_fetch.php (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-102798 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-110252)Record last updated .