WordPress plugin · wpematico
Is WPeMatico RSS Feed Fetcher safe?
Safe on 2.9.1 or newer.
The current version, 2.9.1, is past every affected range on record (15 of 16 records list one; 1 doesn’t, so check it below). Keep it updated and you’re clear of them.
- Flaws on record
- 16
- High or critical
- 2
- Exploited
- none
- Current version
- 2.9.1
- Last updated
- Oct 15, 2026
- Active installs
- 10,000+
Every recorded flaw
- Oct 16, 2026WPeMatico RSS Feed Fetcher: Stored Cross-Site ScriptingCVE-2026-110252 · affects up to 2.9 · reported by WordfenceMedium 5.4
- Sep 27, 2026WPeMatico RSS Feed Fetcher: Does not sanitize imported feed content before storing itCVE-2026-89006 · fixed in 2.8.27 · reported by WPScanMedium 6.8
- Sep 27, 2026WPeMatico RSS Feed Fetcher: Does not perform a capability check before fetching a user-supplied URL and rendering the responseCVE-2026-89003 · fixed in 2.8.27 · reported by WPScanMedium 4.1
- Sep 27, 2026WPeMatico RSS Feed Fetcher: Does not verify that a user running a feed campaign is permitted to publish content or to attribute posts to another accountCVE-2026-89001 · fixed in 2.8.27 · reported by WPScanMedium 4.9
- Sep 27, 2026WPeMatico RSS Feed Fetcher: Does not perform a capability check or validate the destination of a user-supplied feed URL before fetching it server-sideCVE-2026-89000 · fixed in 2.8.27 · reported by WPScanMedium 4.1
- Sep 24, 2026WPeMatico RSS Feed Fetcher: Does not sanitise and escape one of its campaign configuration fieldsCVE-2026-89005 · fixed in 2.8.26 · reported by WPScanMedium 6.8
- Sep 24, 2026WPeMatico RSS Feed Fetcher: Does not verify ownership or authorization before returning a campaign's stored configuration and run logCVE-2026-89004 · fixed in 2.8.26 · reported by WPScanLow 2.7
- Sep 24, 2026WPeMatico RSS Feed Fetcher: Does not sanitize and escape content it retrieves from a user-supplied source before rendering itCVE-2026-89002 · fixed in 2.8.26 · reported by WPScanMedium 6.8
- Aug 21, 2026WPeMatico RSS Feed Fetcher: Unauthorized modification of data that can lead to privilege escalationCVE-2026-19883 · affects up to 2.8.24 · reported by WordfenceHigh 8.8
- Jul 2, 2026Unauthenticated Cross Site Scripting (XSS) in WPeMatico RSS Feed Fetcher <= 2.8.17 versions.CVE-2026-57349 · reported by PatchstackHigh 7.1
- Dec 9, 2025WPeMatico RSS Feed Fetcher: Does not sanitize and escape some of its settingsCVE-2025-13031 · fixed in 2.8.13 · reported by WPScanMedium 5.9
- Nov 5, 2025WPeMatico RSS Feed Fetcher: Server-Side Request ForgeryCVE-2025-11917 · affects up to 2.8.11 · reported by WordfenceMedium 6.4
- Oct 22, 2025WPeMatico RSS Feed Fetcher: Missing AuthorizationCVE-2025-49922 · affects up to 2.8.3 · reported by PatchstackMedium 4.3
- Sep 22, 2025WPeMatico RSS Feed Fetcher: Exposure of Sensitive System Information to an Unauthorized Control SphereCVE-2025-57937 · affects up to 2.8.10 · reported by PatchstackMedium 4.3
- Jul 26, 2025WPeMatico RSS Feed Fetcher: Cross-Site Request ForgeryCVE-2025-8103 · affects up to 2.8.7 · reported by WordfenceMedium 4.3
- Nov 1, 2021WPeMatico RSS Feed Fetcher: Does not escape the Feed URL added to a campaign before outputting it in an attributeCVE-2021-24793 · fixed in 2.6.12 · reported by WPScanMedium 4.8
Records come from the National Vulnerability Database, published by the researchers who found each flaw (Wordfence, Patchstack, WPScan and others); exploited status from CISA; exploit odds from FIRST’s EPSS; current version, installs and closures from wordpress.org, checked daily. Want every plugin on your site checked at once? Run the free website check.
Weekly security brief
The flaws that hit local websites, every Friday.
One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.
Tell us what you're building.
A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.
Not ready to talk yet? Run the free website check and see what Google sees.