LiveActive security incident?Get immediate response
CVE Record

CVE-2023-46629: WordPress Remove Add to Cart WooCommerce Plugin <= 1.4.4 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in themelocation Remove Add to Cart WooCommerce plugin <= 1.4.4.

MediumCVSS 4.3Not 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 WordPress Remove Add to Cart WooCommerce plugin through version 1.4.4. A malicious site could potentially cause a logged-in user’s browser to make an unintended change, with limited integrity impact. The sources do not show active exploitation or a confirmed fix.

Executive priority

Treat this as a moderate WordPress hygiene item, not an emergency based on current evidence. Address it in the next plugin maintenance cycle, sooner for revenue-generating WooCommerce sites.

Technical view

CVE-2023-46629 is CWE-352 affecting themelocation Remove Add to Cart WooCommerce. The provided CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N, scoring 4.3. Impact is limited to integrity; confidentiality and availability are not indicated as affected.

Likely exposure

Exposure is likely limited to WordPress/WooCommerce sites that have the remove-add-to-cart-woocommerce plugin installed at version 1.4.4 or earlier.

Exploitation context

The CVSS vector indicates network reachability, low attack complexity, no attacker privileges, and required user interaction. The source bundle marks KEV as false, and no cited source establishes active exploitation.

Researcher notes

Evidence is limited to the CVE record and Patchstack database entry. The bundle does not provide vulnerable endpoint details, exploit examples, affected action specifics, or a named fixed version. Avoid claiming exploitation without new source evidence.

Mitigation direction

  • Inventory WordPress sites for the remove-add-to-cart-woocommerce plugin.
  • Identify installed plugin versions and flag version 1.4.4 or earlier.
  • Check vendor or Patchstack guidance for a fixed release or official mitigation.
  • Disable or remove the plugin where it is unnecessary or unsupported.
  • Prioritize review on public WooCommerce sites with active administrators.

Validation and detection

  • Confirm plugin presence from WordPress administration or asset inventory.
  • Record exact plugin version for each affected WordPress site.
  • Review Patchstack and vendor sources for current remediation status.
  • Check change logs before assuming any version is fixed.
  • Verify affected sites after remediation no longer run version 1.4.4 or earlier.
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-2023-46629 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
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
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-2023-46629Attack 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
themelocationRemove Add to Cart WooCommerceremove-add-to-cart-woocommerce, n/aunaffected
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.