WPeMatico RSS Feed Fetcher <= 2.8.11 - Authenticated (Subscriber+) Server-Side Request Forgery via wpematico_test_feed
Strategic Overview
- Status
- Patched in 2.8.12
- Affected Plugin
- WPeMatico RSS Feed Fetcher
- Affected Version
<= 2.8.11- CVSS
- 6.4Medium
- Weakness type
- CWE-918 · Server-Side Request Forgery (SSRF)
- CVE
CVE-2025-11917
At a glance
CVE-2025-11917 is a medium-severity Server-Side Request Forgery (SSRF) vulnerability in the WPeMatico RSS Feed Fetcher WordPress plugin, affecting versions <= 2.8.11. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.8.12; sites on affected versions should update now. Disclosed November 2025, reported by Rafshanzani Suhada.
Vulnerability Overview
The WPeMatico RSS Feed Fetcher plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 2.8.11 via the wpematico_test_feed() function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-918: Server-Side Request Forgery (SSRF)
WPeMatico RSS Feed Fetcher <= 2.8.11 carries this weakness at wpematico_test_feed(), and reaching it takes an account at Subscriber level or above. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.
The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. For WPeMatico RSS Feed Fetcher the fix is 2.8.12: builds <= 2.8.11 are affected, anything from 2.8.12 onward is not.
Remediation
Update to version 2.8.12, or a newer patched version
How does WordSec protect against this?
An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WPeMatico RSS Feed Fetcher 2.8.12 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in WPeMatico RSS Feed Fetcher
- 8.8CVE-2026-19883: WPeMatico RSS Feed Fetcher Privilege Escalation
CVE-2026-19883 - 7.2CVE-2026-57349: WPeMatico RSS Feed Fetcher <= 2.8.17 Stored XSS
CVE-2026-57349 - 5.5CVE-2021-24793: WPeMatico RSS Feed Fetcher <= 2.6.11 Admin+ Stored XSS
CVE-2021-24793 - 4.4CVE-2025-13031: WPeMatico RSS Feed Fetcher <= 2.8.12 Stored XSS
CVE-2025-13031 - 4.3CVE-2025-57937: WPeMatico RSS Feed Fetcher <= 2.8.10 Info Exposure
CVE-2025-57937 - 4.3CVE-2025-8103: WPeMatico RSS Feed Fetcher CSRF to Plugin Deactivation
CVE-2025-8103 - 4.3CVE-2025-49922: WPeMatico RSS Feed Fetcher Missing Authorization
CVE-2025-49922
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C