CVE-2025-1562
BaseFortify
Publication date: 2025-06-18
Last updated on: 2025-07-09
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| funnelkit | funnelkit_automations | to 3.6.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-862 | The product does not perform an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the Recover WooCommerce Cart Abandonment, Newsletter, Email Marketing, Marketing Automation By FunnelKit WordPress plugin (versions up to and including 3.5.3). It allows unauthenticated attackers to install arbitrary plugins on the affected WordPress site because the function responsible for installing or activating plugins (install_or_activate_addon_plugins()) lacks proper capability checks and uses a weak nonce hash. This means attackers can bypass authentication and security checks to add plugins that could further compromise the site.
How can this vulnerability impact me? :
The vulnerability can have severe impacts as it allows attackers to install arbitrary plugins without authentication. This can lead to full site compromise, including unauthorized code execution, data theft, site defacement, or further malware infection. The CVSS score of 9.8 indicates a critical severity with high impact on confidentiality, integrity, and availability of the site.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability involves unauthorized arbitrary plugin installation via the Recover WooCommerce Cart Abandonment, Newsletter, Email Marketing, Marketing Automation By FunnelKit plugin for WordPress, due to missing capability checks and weak nonce hashes. Detection can focus on monitoring REST API calls to the endpoint responsible for plugin installation or activation, specifically calls to the `/plugin/install_and_activate` route. You can check your web server or application logs for suspicious POST requests to this endpoint, especially those that attempt to install or activate plugins without proper authentication. Suggested commands to detect suspicious activity: 1. Using grep on web server logs (e.g., Apache or Nginx) to find POST requests to the vulnerable API endpoint: ```bash grep 'POST /wp-json/bwfan/v1/plugin/install_and_activate' /var/log/apache2/access.log ``` 2. Using WP-CLI to list recently installed or activated plugins (to detect unexpected changes): ```bash wp plugin list --status=active ``` 3. Monitoring WordPress debug or security logs for unauthorized plugin installation attempts. 4. If you have access to the WordPress database, you can query the `wp_options` or `wp_plugins` tables to check for recently added plugins. Note: The exact REST API namespace (`bwfan/v1`) and route (`plugin/install_and_activate`) are inferred from Resource 4 describing the vulnerable API endpoint. Because the vulnerability allows unauthenticated attackers to install arbitrary plugins, any unexpected plugin installation or activation should be investigated immediately. [4]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1. Update the Recover WooCommerce Cart Abandonment, Newsletter, Email Marketing, Marketing Automation By FunnelKit plugin to version 3.6.0 or later, where permission checks and nonce verification have been improved to prevent unauthorized plugin installation and activation (as shown in Resources 1, 2, and 3). 2. If updating immediately is not possible, restrict access to the WordPress REST API endpoints related to plugin installation and activation by limiting access to trusted users or IP addresses. 3. Monitor your site for any unauthorized plugin installations or activations and remove any suspicious plugins. 4. Implement additional security measures such as Web Application Firewalls (WAF) to block unauthorized REST API requests. 5. Review user roles and capabilities to ensure only trusted users have plugin installation and activation permissions. 6. Consider temporarily disabling the vulnerable plugin if it is not critical to your siteβs operation until a patch is applied. These steps help prevent exploitation by enforcing proper capability checks and nonce validation introduced in version 3.6.0, as detailed in Resources 1, 2, and 3. [1, 2, 3]