LiveActive security incident?Get immediate response
CVE Record

CVE-2023-52127: WordPress WPC Product Bundles for WooCommerce Plugin <= 7.3.1 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in WPClever WPC Product Bundles for WooCommerce.This issue affects WPC Product Bundles for WooCommerce: from n/a through 7.3.1.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a CSRF issue in the WPC Product Bundles for WooCommerce WordPress plugin through version 7.3.1. It could let an attacker induce a logged-in user’s browser to perform an unintended plugin-related action. The cited scoring indicates limited integrity impact, with no confidentiality or availability impact stated.

Executive priority

Treat this as a targeted maintenance item for WooCommerce properties, not an emergency based on the provided evidence. Prioritize sites where many administrators manage product bundles or where plugin configuration changes could affect sales or customer experience.

Technical view

CVE-2023-52127 is CWE-352 affecting WPClever WPC Product Bundles for WooCommerce, package slug woo-product-bundle, through 7.3.1. CVSS 3.1 is 4.3: network exploitable, low complexity, no attacker privileges, user interaction required, unchanged scope, low integrity impact only.

Likely exposure

Exposure is limited to WordPress/WooCommerce sites running WPC Product Bundles for WooCommerce version 7.3.1 or earlier. Sites not using this plugin, or using versions outside the affected range, are not indicated as affected by the provided sources.

Exploitation context

The source bundle does not cite active exploitation, and the CVE is not listed as KEV. The CVSS vector requires user interaction, consistent with CSRF: attacker success depends on a victim user’s browser being induced to submit an unintended request.

Researcher notes

Evidence is sparse beyond the CVE record and Patchstack entry. The record identifies CSRF, affected range through 7.3.1, and limited integrity impact. No exploit details, fixed version, or active exploitation claim is present in the provided bundle.

Mitigation direction

  • Inventory WordPress sites for the woo-product-bundle plugin and installed version.
  • Check WPClever or Patchstack guidance for the fixed release or recommended mitigation.
  • Update affected installations when a vendor-supported fixed version is identified.
  • Restrict administrative access and reinforce session hygiene for WooCommerce administrators.

Validation and detection

  • Confirm whether WPC Product Bundles for WooCommerce is installed on each WordPress site.
  • Verify installed versions are not 7.3.1 or earlier unless vendor guidance says otherwise.
  • Review vendor advisories for the exact fixed version and remediation notes.
  • Confirm CSRF protections exist for sensitive plugin-changing actions after remediation.
Prepared
Confidence
high
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-52127 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-52127Attack 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
WPCleverWPC Product Bundles for WooCommercewoo-product-bundle, 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.