LiveActive security incident?Get immediate response
CVE Record

CVE-2024-23512: WordPress ProductX – Gutenberg WooCommerce Blocks Plugin <= 3.1.4 is vulnerable to PHP Object Injection

Deserialization of Untrusted Data vulnerability in wpxpo ProductX – WooCommerce Builder & Gutenberg WooCommerce Blocks.This issue affects ProductX – WooCommerce Builder & Gutenberg WooCommerce Blocks: from n/a through 3.1.4.

HighCVSS 8.7Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This affects WordPress sites using the ProductX WooCommerce Builder and Gutenberg WooCommerce Blocks plugin through version 3.1.4. The flaw can let an unauthenticated remote attacker trigger unsafe PHP object handling. Business risk is high because successful exploitation could expose or alter sensitive site data, especially on ecommerce properties.

Executive priority

Treat this as a high-priority WordPress plugin risk for ecommerce sites. Confirm exposure quickly and remediate affected installations, but avoid claiming active compromise without local evidence because the provided sources do not show exploitation in the wild.

Technical view

CVE-2024-23512 is CWE-502 deserialization of untrusted data in the ProductX plugin slug product-blocks through 3.1.4. CVSS 3.1 is 8.7 with network access, no privileges, no user interaction, high attack complexity, scope change, and high confidentiality and integrity impact.

Likely exposure

Exposure is limited to WordPress installations running wpxpo ProductX – WooCommerce Builder & Gutenberg WooCommerce Blocks through version 3.1.4. The bundle does not identify other affected products or hosting environments.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The CVSS vector indicates remote unauthenticated reachability, but high attack complexity means exploitation likely depends on site-specific PHP object conditions.

Researcher notes

Evidence identifies PHP object injection/deserialization only; it does not provide exploit primitives, affected code paths, fixed version, or proof of active exploitation. Validation should focus on plugin presence, version, public exposure, and vendor/Patchstack updates.

Mitigation direction

  • Inventory WordPress sites for the product-blocks plugin and installed version.
  • Prioritize any internet-facing or ecommerce site running version 3.1.4 or earlier.
  • Check vendor and Patchstack guidance for a fixed release or official mitigation.
  • Disable or remove the plugin where no fixed version is available or required.
  • Preserve backups before plugin changes on production WooCommerce sites.

Validation and detection

  • Confirm each site’s ProductX plugin version against the affected range through 3.1.4.
  • Verify remediation state after update, removal, or disablement.
  • Review web and WAF logs for unusual requests to WordPress or plugin endpoints.
  • Check CVE and Patchstack records for updated fix or exploitation information.
  • Document exceptions where the plugin remains installed below or at 3.1.4.
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-2024-23512 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.7 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/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
8.7CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N2.25.8Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.7High
CVSS 3.1 vector shape for CVE-2024-23512Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/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
wpxpoProductX – WooCommerce Builder & Gutenberg WooCommerce Blocksproduct-blocks, 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.