LiveActive security incident?Get immediate response
CVE Record

CVE-2025-32119: WordPress CardGate Payments for WooCommerce plugin <= 3.2.1 - SQL Injection vulnerability

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in CardGate CardGate Payments for WooCommerce cardgate allows Blind SQL Injection.This issue affects CardGate Payments for WooCommerce: from n/a through <= 3.2.1.

HighCVSS 8.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-32119 is a high-severity blind SQL injection issue in the CardGate Payments for WooCommerce WordPress plugin through version 3.2.1. It may allow database information exposure from affected online stores. The source bundle does not name a fixed version or confirm active exploitation.

Executive priority

Treat this as a near-term remediation item for any store using CardGate Payments. Payment-related WordPress plugins are commonly internet-facing, and the reported impact is database confidentiality exposure. Do not delay verification while waiting for exploitation confirmation.

Technical view

The issue is CWE-89 SQL injection in the cardgate plugin, scored CVSS 8.2. The vector is network-accessible, low complexity, unauthenticated, and requires user interaction. Impact is high confidentiality loss, no integrity impact, and low availability impact, with changed scope.

Likely exposure

Exposure is likely limited to WordPress WooCommerce sites using CardGate Payments for WooCommerce version 3.2.1 or earlier. Public storefronts using the plugin should be treated as potentially reachable until verified otherwise.

Exploitation context

The supplied sources describe blind SQL injection but do not provide public exploit status. KEV is false, so active exploitation should not be assumed from this bundle. User interaction is indicated by the CVSS vector.

Researcher notes

Evidence is concise: CVE and Patchstack identify blind SQL injection affecting CardGate Payments for WooCommerce through 3.2.1. The bundle does not include vulnerable parameters, proof-of-concept details, fixed version, or vendor advisory text. Avoid assuming broader WordPress or WooCommerce exposure.

Mitigation direction

  • Inventory WordPress/WooCommerce sites for the cardgate plugin and record installed versions.
  • Prioritize sites running CardGate Payments for WooCommerce version 3.2.1 or earlier.
  • Check CardGate, WordPress plugin, and Patchstack guidance for an official fixed version or mitigation.
  • Disable or remove the plugin where business operations can tolerate it until vendor guidance is confirmed.

Validation and detection

  • Confirm whether each WooCommerce site has the cardgate plugin installed.
  • Verify installed plugin versions against the affected range: through version 3.2.1.
  • Review web application logs for unusual requests involving CardGate payment plugin endpoints.
  • Confirm compensating controls without running exploit payloads or intrusive SQL injection tests.
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-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. 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
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-32119 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
High
CVSS
8.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/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
8.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:L2.84.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.2High
CVSS 3.1 vector shape for CVE-2025-32119Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/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
CardGateCardGate Payments for WooCommercecardgate, 0unaffected
Weakness

CWE details

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

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.