CVE-2026-110252 json
WPeMatico RSS Feed Fetcher <= 2.9 - Unauthenticated Stored Cross-Site Scripting via RSS Feed Content Import
published 24d ago modified 24d ago also EUVD-2026-102798
- cvss
- 5.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 21%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
Is CVE-2026-110252 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 24d ago
Exploit prediction
0.29% chance of exploitation in the next 30 days, higher than 21% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N |
Affected products
- etruel WPeMatico RSS Feed Fetcher
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- github.com /etruel/wpematico/commit/44c4894a0ad92a711c534ad4d822c0b5d7c3dffe
- wordfence.com /threat-intel/vulnerabilities/id/e87fc1bf-af05-4089-a164-8a2e73c68e8c?source=cve
- plugins.trac.wordpress.org /browser/wpematico/tags/2.9/includes/campaign_fetch.php#L400
- plugins.trac.wordpress.org /browser/wpematico/tags/2.9/includes/wpematico_functions.php#L3226
- plugins.trac.wordpress.org /browser/wpematico/tags/2.9/includes/campaign_fetch.php#L777
- plugins.trac.wordpress.org /browser/wpematico/tags/2.9/includes/campaign_fetch.php#L773
- plugins.trac.wordpress.org /browser/wpematico/tags/2.9/includes/wpematico_functions.php#L3326
- plugins.trac.wordpress.org /changeset/3747465/wpematico/trunk/includes/campaign_fetch.php
Sources
- CVE List CVE-2026-110252
- NVD CVE-2026-110252
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.