LiveActive security incident?Get immediate response
CVE Record

CVE-2023-52218: WordPress WooCommerce Tranzila Gateway Plugin <= 1.0.8 is vulnerable to PHP Object Injection

Deserialization of Untrusted Data vulnerability in Anton Bond Woocommerce Tranzila Payment Gateway.This issue affects Woocommerce Tranzila Payment Gateway: from n/a through 1.0.8.

CriticalCVSS 10Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2023-52218 is a critical flaw in the WordPress WooCommerce Tranzila Payment Gateway plugin up to version 1.0.8. An unauthenticated attacker could abuse unsafe PHP deserialization, potentially compromising confidentiality, integrity, and availability of the site. No cited source confirms active exploitation.

Executive priority

Treat as urgent for any store using this payment gateway plugin. The maximum CVSS score and unauthenticated attack path justify rapid inventory and remediation, even without confirmed exploitation.

Technical view

The issue is CWE-502 Deserialization of Untrusted Data / PHP Object Injection in Anton Bond Woocommerce Tranzila Payment Gateway, package woo-tranzila-gateway, affecting versions through 1.0.8. CVSS 3.1 is 10.0 with network access, low complexity, no privileges, no user interaction, changed scope, and high C/I/A impact.

Likely exposure

Exposure is limited to WordPress/WooCommerce sites using the Woocommerce Tranzila Payment Gateway plugin at version 1.0.8 or earlier. Internet-facing stores are higher priority because the CVSS vector indicates unauthenticated network exploitation.

Exploitation context

The source bundle does not include exploit code, known exploitation, or CISA KEV listing. Risk remains high because unauthenticated PHP object injection can be severe, especially where reachable vulnerable code and usable PHP object chains exist.

Researcher notes

Public evidence is sparse: CVE and Patchstack identify the vulnerable plugin, affected range, CWE, and severity. The bundle does not name a fixed version or confirm exploitation. Avoid assuming exploitability details beyond unauthenticated PHP object injection and stated CVSS impacts.

Mitigation direction

  • Inventory WordPress sites for the woo-tranzila-gateway plugin and version.
  • Update if vendor or WordPress plugin guidance identifies a fixed release.
  • If no fixed release is available, disable or remove the plugin after business review.
  • Prioritize payment-processing sites and externally reachable WooCommerce stores.
  • Monitor Patchstack, CVE, and vendor channels for remediation updates.

Validation and detection

  • Confirm whether woo-tranzila-gateway is installed on each WordPress site.
  • Record installed plugin version and compare against affected versions through 1.0.8.
  • Check whether the site is internet-facing and processes WooCommerce payments.
  • Review security logs for unusual unauthenticated requests to plugin-related endpoints.
  • Document compensating controls and any plugin removal or upgrade actions.
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-502: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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-52218 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
Critical
CVSS
10 (3.1)
Known Exploited
No
Published

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

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
10CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H3.96Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

10Critical
CVSS 3.1 vector shape for CVE-2023-52218Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
Anton BondWoocommerce Tranzila Payment Gatewaywoo-tranzila-gateway, n/aunaffected
Weakness

CWE details

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

CWE-502 · source CWE mapping

Deserialization of Untrusted Data

Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.