Security readout for executives and security teams
Plain-English summary
Creative Mail for WordPress had a CSRF flaw in versions 1.5.4 and earlier. An attacker could potentially trick a logged-in WordPress user into causing an unintended plugin action. The supplied evidence rates this medium severity, with low integrity and availability impact and no confidentiality impact.
Executive priority
Treat this as a moderate WordPress plugin exposure. It is not supported as actively exploited in the supplied evidence, but affected public sites should be remediated in normal patch cycles because CSRF can alter site or plugin state through trusted users.
Technical view
CVE-2022-40687 is a CWE-352 CSRF vulnerability in Constant Contact Creative Mail for WordPress through 1.5.4. CVSS 3.1 is 5.4: network reachable, low complexity, no attacker privileges, user interaction required, unchanged scope, no confidentiality impact, low integrity and availability impact.
Likely exposure
Exposure is limited to WordPress sites running the Creative Mail plugin at version 1.5.4 or earlier. Sites not using this plugin, or using a remediated version, are not indicated as affected by the supplied sources.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation. Exploitation is plausible only with victim interaction, consistent with CSRF: a user with an active WordPress session would need to be induced into triggering an unintended request.
Researcher notes
The bundle provides CVE metadata, CVSS vector, affected version range, CWE-352 classification, and a Patchstack reference. It does not include endpoint details, affected actions, nonce behavior, proof of concept, active exploitation, or a named fixed version, so validation should remain version and advisory based.
Mitigation direction
- Inventory WordPress sites for Creative Mail plugin usage.
- Identify any Creative Mail versions at or below 1.5.4.
- Check Constant Contact, WordPress.org, or Patchstack guidance for the fixed version.
- Update, disable, or remove affected plugin instances per vendor guidance.
- Prioritize sites where privileged WordPress users manage email marketing.
Validation and detection
- Confirm installed plugin name and version on each WordPress site.
- Review plugin changelog or vendor advisory for remediation status.
- Verify affected versions are no longer present after remediation.
- Check WordPress audit logs for unusual plugin configuration changes.
- Document exceptions where update or removal is delayed.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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.
Open ATT&CK lookupCVE-2022-40687 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L2.82.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.