CVE-2025-8103
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-07-26

Last updated on: 2025-07-29

Assigner: Wordfence

Description
The WPeMatico RSS Feed Fetcher plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.8.7. This is due to missing nonce validation in the handle_feedback_submission() function. This makes it possible for unauthenticated attackers to deactivate the plugin via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-07-26
Last Modified
2025-07-29
Generated
2026-05-07
AI Q&A
2025-07-26
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
wpematico wpematico 2.8.8
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-352 The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2025-8103 is a Cross-Site Request Forgery (CSRF) vulnerability in the WPeMatico RSS Feed Fetcher WordPress plugin, affecting all versions up to and including 2.8.7. The vulnerability arises because the plugin's handle_feedback_submission() function lacks nonce validation, allowing an attacker to trick a site administrator into performing an unwanted action, such as deactivating the plugin, by sending a forged request. This means an attacker can cause the plugin to be deactivated without the administrator's explicit consent. [2, 4]


How can this vulnerability impact me? :

This vulnerability can impact you by allowing an unauthenticated attacker to deactivate the WPeMatico plugin on your WordPress site if they can trick an administrator into clicking a malicious link or performing a certain action. Deactivation of the plugin could disrupt automated RSS feed fetching and autoblogging functionality, potentially affecting content updates and site operations. Although it does not directly compromise data confidentiality or integrity, it causes availability issues by disabling plugin features. [2, 4]


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

This vulnerability is a Cross-Site Request Forgery (CSRF) issue in the WPeMatico WordPress plugin versions up to 2.8.7, allowing unauthenticated attackers to deactivate the plugin via forged requests. Detection involves monitoring for unauthorized or unexpected plugin deactivation requests, especially AJAX requests lacking nonce verification related to feedback submission. On the server or network, you can look for HTTP POST requests to admin-ajax.php with the action parameter set to handle_feedback_submission without a valid nonce. For example, using command-line tools, you might inspect web server logs or capture traffic with commands like: - To search web server logs for suspicious AJAX feedback submissions: grep "action=handle_feedback_submission" /var/log/apache2/access.log | grep -v "_wpnonce" - To capture and filter HTTP POST requests to admin-ajax.php using tcpdump: sudo tcpdump -A -s 0 'tcp port 80 and (((ip[2:2] - ((ip[0]&0xf)<<2)) - ((tcp[12]&0xf0)>>2)) != 0)' and then filter for "handle_feedback_submission" in the payload. - Using WP-CLI or WordPress logs, check for unexpected plugin deactivation events or audit logs if available. Note that specific detection commands depend on your environment and logging setup, but focusing on AJAX requests to handle_feedback_submission without nonce validation is key. [2, 4]


What immediate steps should I take to mitigate this vulnerability?

To mitigate this vulnerability immediately, update the WPeMatico plugin to version 2.8.8 or later, where the CSRF issue has been fixed by implementing nonce verification for AJAX feedback submissions and other security enhancements. If updating immediately is not possible, restrict access to the WordPress admin area to trusted users only, and consider disabling the plugin temporarily to prevent exploitation. Additionally, monitor and audit plugin deactivation actions to detect any unauthorized attempts. Applying the official patch or update is the most effective mitigation. [2, 4, 1]


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