LiveActive security incident?Get immediate response
CVE Record

CVE-2024-13795: Ecwid by Lightspeed Ecommerce Shopping Cart <= 6.12.27 - Cross-Site Request Forgery to Send Deactivation Message

The Ecwid by Lightspeed Ecommerce Shopping Cart plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 6.12.27. This is due to missing or incorrect nonce validation on the ecwid_deactivate_feedback() function. This makes it possible for unauthenticated attackers to send deactivation messages on behalf of a site owner via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This WordPress Ecwid ecommerce plugin flaw lets an attacker trick a logged-in site administrator into sending a deactivation feedback message. It does not expose customer data or directly take over the store, but it can cause unauthorized actions in an admin context.

Executive priority

Treat as a routine but real WordPress hygiene issue. Prioritize affected ecommerce sites, but this is not currently supported as an emergency exposure based on the supplied sources.

Technical view

CVE-2024-13795 is a CSRF issue in ecwid_deactivate_feedback() caused by missing or incorrect nonce validation. It affects Ecwid by Lightspeed Ecommerce Shopping Cart versions up to and including 6.12.27. CVSS is 4.3 with low integrity impact and required user interaction.

Likely exposure

Exposure is limited to WordPress sites running the Ecwid by Lightspeed Ecommerce Shopping Cart plugin at version 6.12.27 or earlier, especially where administrators browse while authenticated.

Exploitation context

The source bundle does not show active exploitation, and CISA KEV is false. Exploitation requires convincing a logged-in administrator to perform an action such as clicking a crafted link.

Researcher notes

The main technical evidence is the missing or incorrect nonce validation on ecwid_deactivate_feedback(). The bundle does not provide exploit telemetry, broader impact, or a clearly named fixed version, so validation should stay source-grounded.

Mitigation direction

  • Inventory WordPress sites using the Ecwid by Lightspeed plugin.
  • Confirm whether installed versions are 6.12.27 or earlier.
  • Check Ecwid or WordPress plugin guidance for the fixed release.
  • Update the plugin when a vendor-supported fixed version is confirmed.
  • Train administrators to avoid untrusted links while logged into WordPress.

Validation and detection

  • Check plugin version across production and staging WordPress sites.
  • Review whether the plugin is active on public ecommerce sites.
  • Look for unexpected deactivation feedback activity in WordPress or application logs.
  • Confirm patched code includes proper nonce validation for deactivation feedback.
  • Document any sites awaiting vendor-confirmed remediation.
Prepared
Confidence
medium
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-2024-13795 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
4.3 (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:N

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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2024-13795Attack 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:N

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
ecwidEcwid by Lightspeed Ecommerce Shopping Cart0unaffected
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.