CVE-2025-11976 MEDIUM

CVE-2025-11976: FuseWP – WordPress User Sync to Email List & Marketing Automation (Mailchimp, Constant Contact, ActiveCampaign etc.) <= 1.1.23.0 - Cross-Site Request Forgery to Sync Rule Creation

Vendor Fusewp
Product FuseWP – WordPress User Sync to Email List & Marketing Automation (Mailchimp, Constant Contact, ActiveCampaign etc.)
Weakness CWE-352 · CSRF
Published October 25, 2025
Last update April 8, 2026

CVSS base score

4.3/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction Required
Confidentiality None
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

What the vulnerability does

01Description

The FuseWP – WordPress User Sync to Email List & Marketing Automation (Mailchimp, Constant Contact, ActiveCampaign etc.) plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.1.23.0. This is due to missing or incorrect nonce validation on the save_changes function. This makes it possible for unauthenticated attackers to add or edit sync rules via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Explanation of Vulnerability in Simple Terms

02Summary

The FuseWP plugin for WordPress is vulnerable to cross-site request forgery (CSRF) attacks. An attacker can craft a malicious webpage that, when visited by a logged-in WordPress admin, performs unwanted actions on the site without the admin's knowledge or consent. This affects all versions up to 1.1.23.0. Site owners should update the plugin to a version newer than 1.1.23.0 when available.

What an attacker can do

03Attacker Capabilities

Perform unwanted actions on a WordPress site by tricking an admin into visiting a malicious webpage.

Potential impact on your site

04Site Impact

An attacker can modify plugin settings or trigger unintended actions affecting user sync and email list management.

Conditions required to exploit

05Prerequisites

Admin must be logged into WordPress and visit a page controlled by the attacker.

Key dates

06Disclosure timeline

October 25, 2025 CVE published
April 8, 2026 Record updated

Related vulnerabilities

08Related CVE