Freesoul Deactivate Plugins <= 2.1.3 - Cross-Site Request Forgery via eos_dp_pro_delete_transient
Strategic Overview
- Status
- Patched in 2.1.4
- Affected Version
< 2.1.4- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2023-46188
At a glance
CVE-2023-46188 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Freesoul Deactivate Plugins WordPress plugin, affecting versions < 2.1.4. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.1.4; sites on affected versions should update now. Disclosed October 2023, reported by Abdi Pranata.
Vulnerability Overview
The Freesoul Deactivate Plugins – Plugin manager and cleanup plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to 2.1.4 (exclusive). This is due to missing or incorrect nonce validation on the eos_dp_pro_delete_transient function. This makes it possible for unauthenticated attackers to invoke this function via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in Freesoul Deactivate Plugins < 2.1.4 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Freesoul Deactivate Plugins the fix is 2.1.4: builds < 2.1.4 are affected, anything from 2.1.4 onward is not.
Remediation
Update to version 2.1.4, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Freesoul Deactivate Plugins: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Freesoul Deactivate Plugins 2.1.4 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Freesoul Deactivate Plugins – Disable plugins on individual WordPress pages
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C