CVE-2025-11917 json
WPeMatico RSS Feed Fetcher <= 2.8.11 - Authenticated (Subscriber+) Server-Side Request Forgery via wpematico_test_feed
published last yr. modified 24d ago also EUVD-2025-37792
- cvss
- 6.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 15%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
Is CVE-2025-11917 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
- last yr.
Exploit prediction
0.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N |
Affected products
- etruel WPeMatico RSS Feed Fetcher
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
- Technology feeds
References
- github.com /etruel/wpematico/commit/7a281dcfc0868490d62caee54f3b743708fed7cf
- wordfence.com /threat-intel/vulnerabilities/id/5a1c6377-c2a7-4344-86bd-d2797db19469?source=cve
- plugins.trac.wordpress.org /browser/wpematico/tags/2.8.11/app/campaign_edit.php#L24
- plugins.trac.wordpress.org /browser/wpematico/tags/2.8.11/app/wpematico_functions.php#L1249
- plugins.trac.wordpress.org /browser/wpematico/tags/2.8.11/app/wpematico_functions.php#L1260
Sources
- CVE List CVE-2025-11917
- NVD CVE-2025-11917
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.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.