WordPress security changelog
HIGH CVE-2025-48101 Deferred

Constant Contact for WordPress: Code execution

Constant Contact for WordPress is affected by code execution. Exposure depends on how the affected operation is made reachable by the site. Successful exploitation can run attacker-controlled code in the WordPress hosting account.

CVE / CNA score 8.8 CVSS 3.1 · audit@patchstack.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
Constant Contact for WordPress
Plugin slug
constant-contact-api
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Sep 09, 2025
Weakness
CWE-502 — Deserialization of Untrusted Data

This CVE was published Sep 09, 2025 and is one of 1 known issue for this plugin.

Update, patch or deactivate.

Update Constant Contact for WordPress to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Technical description

Deserialization of Untrusted Data vulnerability in webdevstudios Constant Contact for WordPress allows Object Injection. This issue affects Constant Contact for WordPress: from n/a through 4.1.1.

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

Primary and upstream sources