LiveActive security incident?Get immediate response
CVE Record

CVE-2022-40686: WordPress Creative Mail plugin <= 1.5.4 - Cross-Site Request Forgery (CSRF) vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in Creative Mail plugin <= 1.5.4 on WordPress.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-40686 affects the Creative Mail WordPress plugin by Constant Contact through version 1.5.4. It is a CSRF issue, meaning a user could be tricked into causing an unwanted action in WordPress. Reported impact is limited integrity and availability, not confidentiality.

Executive priority

Treat this as a moderate-priority WordPress plugin issue. It is not reported as actively exploited here, but affected public websites should be identified and remediated through normal vulnerability management because CSRF can cause unwanted site changes.

Technical view

The vulnerability is CWE-352 in Creative Mail for WordPress <= 1.5.4. CVSS 3.1 is 5.4: network-accessible, low complexity, no attacker privileges, user interaction required, unchanged scope, no confidentiality impact, and low integrity and availability impact.

Likely exposure

Exposure is limited to WordPress sites that have the Creative Mail plugin installed at version 1.5.4 or earlier. Sites without this plugin, or with versions outside the affected range, are not indicated as affected by the provided sources.

Exploitation context

The source bundle does not cite active exploitation, and KEV status is false. The CVSS vector indicates exploitation requires user interaction, consistent with CSRF risk where a victim is induced to trigger an unintended request.

Researcher notes

Evidence is sparse in the provided bundle. The public data establishes affected product, version range, CWE, CVSS vector, and Patchstack reference, but does not describe the specific vulnerable action, patch version, exploit availability, or in-the-wild activity.

Mitigation direction

  • Inventory WordPress sites for the Creative Mail plugin and version.
  • If version is <= 1.5.4, check vendor or Patchstack guidance for a fixed release.
  • Upgrade only to a vendor-supported version identified as remediated.
  • Disable the plugin temporarily if business risk is unacceptable and no fix is confirmed.
  • Review WordPress user roles and remove unnecessary privileged access.

Validation and detection

  • Confirm whether Creative Mail is installed on each WordPress site.
  • Record the installed plugin version and compare it with <= 1.5.4.
  • Review vendor, WordPress plugin, or Patchstack advisories for remediation status.
  • Check whether compensating controls require re-authentication or nonce protection for sensitive actions.
  • Document sites still running affected versions for remediation tracking.
Prepared
Confidence
medium
Sources
3

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-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 lookup
cve · low confidence lookup

CVE-2022-40686 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
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

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2022-40686Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Constant ContactCreative Mail (WordPress plugin)<= 1.5.4Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

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.