CVE-2026-0674: WordPress Campaign Monitor for WordPress plugin <= 2.9.1 - Broken Access Control vulnerability
Missing Authorization vulnerability in Campaign Monitor Campaign Monitor for WordPress allows Exploiting Incorrectly Configured Access Control Security Levels.
This issue affects Campaign Monitor for WordPress: from n/a through 2.9.1.
Security readout for executives and security teams
Plain-English summary
This is a medium-risk WordPress plugin access-control issue in Campaign Monitor for WordPress. An authenticated user with low privileges may be able to perform an action the plugin should have restricted. The reported impact is limited integrity loss, not data theft or site outage.
Executive priority
Treat as a routine but time-bound plugin remediation. Prioritize internet-facing WordPress sites, especially where many authenticated users exist. It is not currently supported as an emergency exploitation case by the provided sources.
Technical view
CVE-2026-0674 is a CWE-862 missing authorization flaw affecting Campaign Monitor for WordPress through 2.9.1, package slug forms-for-campaign-monitor. CVSS 3.1 is 4.3 with network access, low complexity, low privileges, no user interaction, unchanged scope, and low integrity impact only.
Likely exposure
Exposure is limited to WordPress sites with the Campaign Monitor for WordPress plugin installed at an affected version. The CVE data identifies versions through 2.9.1, but source details are sparse.
Exploitation context
No active exploitation is stated in the supplied sources, and this CVE is not listed as KEV. The scoring indicates exploitation requires an authenticated low-privilege account and could affect plugin-controlled integrity.
Researcher notes
The source bundle has limited public detail. CVE text says affected through 2.9.1, while the Patchstack URL title references 2.9.0. Validate exact affected and fixed versions against vendor or Patchstack before closing findings.
Mitigation direction
Inventory WordPress sites for the forms-for-campaign-monitor plugin.
Check vendor and Patchstack guidance for the confirmed fixed version.
Update the plugin when an approved fixed release is available.
Disable the plugin where it is unnecessary or cannot be remediated promptly.
Limit WordPress accounts with access to plugin-related administration paths.
Validation and detection
Confirm installed plugin versions across production and staging WordPress sites.
Review WordPress users and roles for unnecessary low-privilege accounts.
Check audit logs for unexpected plugin setting or form changes.
In staging, verify low-privilege users cannot change plugin-controlled settings.
Track Patchstack or CVE updates for clarified affected and fixed versions.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-862 · source CWE mapping
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.