CVE-2025-11917: CWE-918 Server-Side Request Forgery (SSRF) in etruel WPeMatico RSS Feed Fetcher
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.
AI Analysis
Technical Summary
CVE-2025-11917 identifies a Server-Side Request Forgery (SSRF) vulnerability in the WPeMatico RSS Feed Fetcher plugin for WordPress, specifically in the wpematico_test_feed() function. This vulnerability affects all versions up to and including 2.8.11. SSRF vulnerabilities allow an attacker to abuse a vulnerable server to send crafted requests to internal or external systems that the server can reach but the attacker cannot directly access. In this case, an authenticated attacker with at least Subscriber-level privileges can trigger the SSRF without requiring additional user interaction. The attacker can leverage this to make arbitrary HTTP requests originating from the web application server, potentially querying internal services, accessing sensitive data, or modifying information within internal networks. The vulnerability has a CVSS 3.1 base score of 6.4, indicating medium severity, with the vector showing network attack vector, low attack complexity, privileges required, no user interaction, and a scope change. No patches or exploits are currently publicly available, but the risk remains significant due to the potential for internal network reconnaissance and data manipulation. The vulnerability is categorized under CWE-918, which covers SSRF issues. Given the widespread use of WordPress and the popularity of RSS feed plugins, this vulnerability poses a notable risk to websites using WPeMatico, especially those with internal services accessible from the web server.
Potential Impact
For European organizations, this SSRF vulnerability can lead to unauthorized internal network access, potentially exposing sensitive internal services that are not directly accessible from the internet. Attackers could use this to gather information about internal infrastructure, bypass firewall restrictions, or manipulate internal data, impacting confidentiality and integrity. Although availability impact is low, the breach of internal services could facilitate further attacks or data exfiltration. Organizations running WordPress sites with the WPeMatico plugin, especially those integrating internal APIs or services accessible from the web server, are at risk. The medium severity rating reflects the need for attention but also the requirement for some level of authentication, which limits exposure to external unauthenticated attackers. However, given the common practice of granting Subscriber-level access to users or contributors, the attack surface remains significant. This vulnerability could be exploited in targeted attacks against European businesses, government websites, or media outlets relying on WordPress and this plugin.
Mitigation Recommendations
1. Immediately audit WordPress installations to identify the presence of the WPeMatico RSS Feed Fetcher plugin and its version. 2. Restrict or remove the plugin if it is not essential to reduce attack surface. 3. Monitor for updates from the vendor or WordPress plugin repository and apply patches as soon as they become available. 4. Limit Subscriber-level user accounts and review user privileges to minimize the number of users who can exploit this vulnerability. 5. Implement network segmentation and firewall rules to restrict the web server's ability to access sensitive internal services or administrative interfaces. 6. Use Web Application Firewalls (WAFs) to detect and block suspicious SSRF patterns or unusual outbound requests from the web server. 7. Conduct internal scans and penetration tests to identify if internal services are exposed or vulnerable to SSRF exploitation. 8. Educate administrators and developers about SSRF risks and secure coding practices to prevent similar issues in custom plugins or themes.
Affected Countries
Germany, United Kingdom, France, Netherlands, Italy, Spain, Poland
CVE-2025-11917: CWE-918 Server-Side Request Forgery (SSRF) in etruel WPeMatico RSS Feed Fetcher
Description
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.
AI-Powered Analysis
Technical Analysis
CVE-2025-11917 identifies a Server-Side Request Forgery (SSRF) vulnerability in the WPeMatico RSS Feed Fetcher plugin for WordPress, specifically in the wpematico_test_feed() function. This vulnerability affects all versions up to and including 2.8.11. SSRF vulnerabilities allow an attacker to abuse a vulnerable server to send crafted requests to internal or external systems that the server can reach but the attacker cannot directly access. In this case, an authenticated attacker with at least Subscriber-level privileges can trigger the SSRF without requiring additional user interaction. The attacker can leverage this to make arbitrary HTTP requests originating from the web application server, potentially querying internal services, accessing sensitive data, or modifying information within internal networks. The vulnerability has a CVSS 3.1 base score of 6.4, indicating medium severity, with the vector showing network attack vector, low attack complexity, privileges required, no user interaction, and a scope change. No patches or exploits are currently publicly available, but the risk remains significant due to the potential for internal network reconnaissance and data manipulation. The vulnerability is categorized under CWE-918, which covers SSRF issues. Given the widespread use of WordPress and the popularity of RSS feed plugins, this vulnerability poses a notable risk to websites using WPeMatico, especially those with internal services accessible from the web server.
Potential Impact
For European organizations, this SSRF vulnerability can lead to unauthorized internal network access, potentially exposing sensitive internal services that are not directly accessible from the internet. Attackers could use this to gather information about internal infrastructure, bypass firewall restrictions, or manipulate internal data, impacting confidentiality and integrity. Although availability impact is low, the breach of internal services could facilitate further attacks or data exfiltration. Organizations running WordPress sites with the WPeMatico plugin, especially those integrating internal APIs or services accessible from the web server, are at risk. The medium severity rating reflects the need for attention but also the requirement for some level of authentication, which limits exposure to external unauthenticated attackers. However, given the common practice of granting Subscriber-level access to users or contributors, the attack surface remains significant. This vulnerability could be exploited in targeted attacks against European businesses, government websites, or media outlets relying on WordPress and this plugin.
Mitigation Recommendations
1. Immediately audit WordPress installations to identify the presence of the WPeMatico RSS Feed Fetcher plugin and its version. 2. Restrict or remove the plugin if it is not essential to reduce attack surface. 3. Monitor for updates from the vendor or WordPress plugin repository and apply patches as soon as they become available. 4. Limit Subscriber-level user accounts and review user privileges to minimize the number of users who can exploit this vulnerability. 5. Implement network segmentation and firewall rules to restrict the web server's ability to access sensitive internal services or administrative interfaces. 6. Use Web Application Firewalls (WAFs) to detect and block suspicious SSRF patterns or unusual outbound requests from the web server. 7. Conduct internal scans and penetration tests to identify if internal services are exposed or vulnerable to SSRF exploitation. 8. Educate administrators and developers about SSRF risks and secure coding practices to prevent similar issues in custom plugins or themes.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-10-17T14:18:30.580Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 690af19c063e7c5f011fbd3c
Added to database: 11/5/2025, 6:41:32 AM
Last enriched: 11/12/2025, 8:05:22 AM
Last updated: 12/19/2025, 8:19:28 PM
Views: 58
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-12874: CWE-444 Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') in Quest Coexistence Manager for Notes
MediumCVE-2025-14967: SQL Injection in itsourcecode Student Management System
MediumCVE-2025-14966: SQL Injection in FastAdmin
MediumCVE-2025-14964: Stack-based Buffer Overflow in TOTOLINK T10
CriticalCVE-2025-14965: Path Traversal in 1541492390c yougou-mall
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.