CVE-2025-11917
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-11-05

Last updated on: 2025-11-06

Assigner: Wordfence

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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-11-05
Last Modified
2025-11-06
Generated
2026-05-09
AI Q&A
2025-11-05
EPSS Evaluated
2026-05-08
NVD
EUVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
etruel wpematico 2.8.11
etruel wpematico 2.8.12
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

The vulnerability in the WPeMatico RSS Feed Fetcher WordPress plugin (up to version 2.8.11) is a Server-Side Request Forgery (SSRF) issue in the wpematico_test_feed() function. It allows authenticated users with Subscriber-level access or higher to make the web application send requests to arbitrary locations, including internal network services. This can be exploited to query or modify information from internal services that are otherwise inaccessible externally. [1]


How can this vulnerability impact me? :

This vulnerability can impact you by allowing attackers with low-level authenticated access to make the server perform unauthorized web requests to internal or external systems. This can lead to unauthorized information disclosure, manipulation of internal services, or potentially further attacks within your internal network, bypassing network restrictions. [1]


How can this vulnerability be detected on my network or system? Can you suggest some commands?

Detection of this vulnerability involves checking if the WPeMatico plugin version is 2.8.11 or earlier, as these versions are vulnerable. Additionally, monitoring for unauthorized AJAX requests to the wpematico_test_feed() function from users with Subscriber-level access or above can indicate exploitation attempts. Since the vulnerability allows SSRF via the feed test function, you can look for unusual outbound HTTP requests originating from the WordPress server to internal or arbitrary external IPs. Commands to assist detection could include: 1. Checking the plugin version installed on your WordPress site (e.g., via WP-CLI): `wp plugin list | grep wpematico` 2. Monitoring web server logs for POST requests to admin-ajax.php with action=wpematico_test_feed from low-privilege users. 3. Using network monitoring tools or firewall logs to detect unexpected outbound HTTP requests from the web server to internal IP ranges or unusual external destinations. 4. Example command to search web server logs for suspicious AJAX calls: `grep 'action=wpematico_test_feed' /var/log/apache2/access.log` or equivalent for your web server. 5. Using WordPress debug logs or custom logging to track calls to wpematico_test_feed and the user capabilities invoking it. These steps help identify if the vulnerable function is being accessed improperly or if SSRF attempts are occurring. [1, 4]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include: 1. Update the WPeMatico plugin to version 2.8.12 or later, where the vulnerability is fixed by adding capability checks, nonce validation, URL parameter sanitization, and private IP blocking. 2. If immediate update is not possible, restrict access to the wpematico_test_feed AJAX endpoint to only trusted users with the 'manage_options' capability, preventing Subscriber-level users from invoking it. 3. Implement web application firewall (WAF) rules to block unauthorized POST requests to admin-ajax.php with action=wpematico_test_feed from low-privilege users. 4. Monitor and audit user roles and permissions to ensure no unauthorized users have elevated access. 5. Consider temporarily disabling the feed testing feature if feasible until the plugin is updated. These steps reduce the risk of exploitation by enforcing proper permission checks and request validation as introduced in the patched version. [1, 4]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart