LiveActive security incident?Get immediate response
CVE Record

CVE-2022-44740: WordPress Creative Mail plugin <= 1.5.4 - Multiple Cross-Site Request Forgery (CSRF) vulnerabilities

Multiple Cross-Site Request Forgery (CSRF) vulnerabilities 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

This is a medium-severity CSRF issue in the Creative Mail WordPress plugin through version 1.5.4. An attacker could potentially cause a logged-in user to perform unintended plugin actions, affecting integrity or availability. The provided sources do not show data theft impact or confirmed exploitation.

Executive priority

Treat as a routine but timely WordPress plugin remediation item. It is not shown as actively exploited in the provided sources, but exposed sites running affected versions should be updated or decommissioned to reduce preventable operational risk.

Technical view

CVE-2022-44740 covers multiple CWE-352 CSRF vulnerabilities in Constant Contact Creative Mail for WordPress versions <= 1.5.4. CVSS 3.1 is 5.4 with network access, low complexity, no attacker privileges, required user interaction, and low integrity and availability impact.

Likely exposure

Exposure is limited to WordPress sites with the Creative Mail by Constant Contact plugin installed at version 1.5.4 or earlier. The source bundle does not provide install prevalence, fixed-version details, or affected endpoint specifics.

Exploitation context

The CVSS vector indicates a remote attacker needs user interaction but no account. This is consistent with CSRF, where a logged-in site user may be induced into an unintended action. CISA KEV status is false, and the bundle provides no active-exploitation evidence.

Researcher notes

The bundle identifies the vulnerability class, affected product, affected version range, CWE, and CVSS vector, but not specific vulnerable actions or a fixed release. Avoid assuming endpoint behavior. Validation should focus on plugin presence, versioning, and vendor-published remediation status.

Mitigation direction

  • Inventory WordPress sites for the Creative Mail by Constant Contact plugin.
  • Prioritize sites running Creative Mail version 1.5.4 or earlier.
  • Check Patchstack and WordPress plugin guidance for patched versions or vendor mitigation.
  • Update the plugin if vendor guidance identifies a safe fixed release.
  • Disable or remove the plugin where it is not business-required.

Validation and detection

  • Confirm whether Creative Mail is installed on each WordPress property.
  • Record the installed plugin version and compare it against <= 1.5.4.
  • Review admin activity for unexpected Creative Mail configuration or availability changes.
  • Verify remediation against Patchstack, CVE, and WordPress plugin developer information.
Prepared
Confidence
high
Sources
4

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-44740 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
3Source 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-44740Attack 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.