LiveActive security incident?Get immediate response
CVE Record

CVE-2023-47519: WordPress WooCommerce Product Table Lite Plugin <= 2.6.2 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in WC Product Table WooCommerce Product Table Lite.This issue affects WooCommerce Product Table Lite: from n/a through 2.6.2.

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 WooCommerce Product Table Lite plugin through version 2.6.2. A targeted user interaction could let an attacker cause an unintended low-impact change in WordPress. The sources do not identify the exact impacted action or a confirmed fixed version.

Executive priority

Treat this as a routine but timely WordPress plugin remediation item. It is not presented as actively exploited, but affected public sites should be inventoried and remediated because CSRF can alter site state when a privileged user is induced to interact.

Technical view

CVE-2023-47519 is CWE-352 cross-site request forgery affecting wc-product-table-lite through 2.6.2. CVSS 3.1 is 4.3, network-reachable, low attack complexity, no attacker privileges, user interaction required, and low integrity impact only. Available sources do not provide endpoint, nonce, role, or patch details.

Likely exposure

Exposure is limited to WordPress sites running WooCommerce Product Table Lite version 2.6.2 or earlier. Sites not using this plugin are not indicated as affected.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and no source here confirms active exploitation. Exploitation requires user interaction, consistent with CSRF, but the precise victim role and action are not documented.

Researcher notes

Evidence is sparse. The bundle provides CVSS, CWE, affected package, and Patchstack reference, but not vulnerable endpoint, missing nonce detail, privilege context, or fixed version. Validate exposure by installed plugin version and rely on vendor/Patchstack updates for remediation specifics.

Mitigation direction

  • Inventory WordPress sites for wc-product-table-lite installations and versions.
  • Check vendor and Patchstack guidance for a fixed release or official mitigation.
  • Update the plugin if a vendor-supported fixed version is available.
  • Disable or remove the plugin where no fix exists and business use is not required.
  • Restrict administrative access and reinforce anti-CSRF controls where compensating controls are available.

Validation and detection

  • Confirm whether WooCommerce Product Table Lite is installed on each WordPress site.
  • Record installed plugin versions and flag version 2.6.2 or earlier.
  • Review vendor, CVE, and Patchstack advisories for current remediation details.
  • Check WordPress administrative audit logs for unexpected plugin setting changes.
  • Verify any implemented update or removal in staging before production rollout.
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-47519 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-47519Attack 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
WC Product TableWooCommerce Product Table Litewc-product-table-lite, 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.