CVE-2025-11975 MEDIUM

CVE-2025-11975: FuseWP – WordPress User Sync to Email List & Marketing Automation (Mailchimp, Constant Contact, ActiveCampaign etc.) <= 1.1.23.0 - Missing Authorization to Authenticated (Subscriber+) Sync Rule Creation

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

CVSS base score

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

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 unauthorized modification of data due to a missing capability check on the save_changes() function in all versions up to, and including, 1.1.23.0. This makes it possible for unauthenticated attackers to add and edit sync rules.

Explanation of Vulnerability in Simple Terms

02Summary

The FuseWP plugin for WordPress does not properly check user permissions before allowing certain actions. A logged-in user with low privileges can modify data they should not have access to. The vulnerability affects all versions up to 1.1.23.0. Site administrators should update the plugin to a version newer than 1.1.23.0 when available.

What an attacker can do

03Attacker Capabilities

A low-privilege logged-in user can modify data they should not have permission to change.

Potential impact on your site

04Site Impact

Unauthorized users could alter plugin settings, email list configurations, or marketing automation data tied to your email service integrations.

Conditions required to exploit

05Prerequisites

Attacker must have a low-privilege WordPress user account (e.g., subscriber or contributor role).

Key dates

06Disclosure timeline

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