FuseWP <= 1.1.24.2 - Cross-Site Request Forgery to Sync Rule Status Toggle
Strategic Overview
- Status
- Patched in 1.1.25.2
- Affected Plugin
- FuseWP – WordPress User Sync to Email List & Marketing Automation (Mailchimp, Constant Contact, ActiveCampaign etc.)
- Affected Version
<= 1.1.24.2- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2026-5582
At a glance
CVE-2026-5582 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the FuseWP WordPress plugin, affecting versions <= 1.1.24.2. 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 1.1.25.2; sites on affected versions should update now. Disclosed July 2026, reported by Deadbee.
Vulnerability Overview
The FuseWP plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.1.24.2. This is due to missing nonce verification on the toggle_sync_status() function. This makes it possible for unauthenticated attackers to toggle the status of sync rules (enable/disable) 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)
FuseWP <= 1.1.24.2 carries this weakness at toggle_sync_status(), and reaching it 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 FuseWP the fix is 1.1.25.2: builds <= 1.1.24.2 are affected, anything from 1.1.25.2 onward is not.
Remediation
Update to version 1.1.25.2, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to FuseWP: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: FuseWP 1.1.25.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in FuseWP – WordPress User Sync to Email List & Marketing Automation (Mailchimp, Constant Contact, ActiveCampaign etc.)
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C