CVE-2026-34902: WooCommerce Product Table Lite XSS Vulnerability (v4.6.3 & Earlier)
WooCommerce Product Table Lite, a popular WordPress plugin for displaying product catalogs in table format, contains an unauthenticated cross-site scripting (XSS) vulnerability in versions 4.6.3 and earlier. An attacker can inject malicious JavaScript code that executes in the browsers of site visitors without needing to log in or have special permissions. This allows attackers to steal session cookies, redirect users to phishing pages, capture form data, or deface content—all while appearing to come from your trusted website.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 7.1 HIGH · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
- Weaknesses (CWE)
- CWE-79
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-06-15 / 2026-06-17
NVD description (verbatim)
Unauthenticated Cross Site Scripting (XSS) in WooCommerce Product Table Lite <= 4.6.3 versions.
1 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-34902 is a reflected or stored XSS flaw (CWE-79) in WooCommerce Product Table Lite that bypasses authentication requirements. The vulnerability exists in versions up to and including 4.6.3. The attack vector is network-based with low attack complexity, requiring only user interaction (clicking a malicious link or visiting a compromised page). The scope is changed, meaning the attacker can impact resources beyond the vulnerable component itself. With a CVSS 3.1 score of 7.1 (HIGH), the vulnerability carries moderate confidentiality, integrity, and availability impact.
Business impact
E-commerce sites relying on this plugin face direct threats to customer trust and transaction security. Attackers can harvest customer data, inject fake product reviews or pricing, or install malware-delivery scripts that persist across page views. Because WooCommerce powers approximately 38% of all e-commerce sites, widespread use of this plugin means a large attack surface. Remediation delays increase exposure time and regulatory risk under data protection laws (GDPR, CCPA). Brand reputation damage and potential liability for compromised customer information represent significant financial exposure.
Affected systems
WordPress installations using WooCommerce Product Table Lite plugin version 4.6.3 or earlier are affected. The plugin is commonly used on small- to medium-sized e-commerce sites to improve product browsing experience. Sites that have auto-updates disabled or manual update workflows are at highest immediate risk. The vulnerability requires no special server configuration or environment—any standard WordPress + WooCommerce setup is vulnerable.
Exploitability
Exploitation is straightforward and does not require authentication. An attacker crafts a URL or form containing malicious JavaScript, then tricks or socially engineers a site visitor into clicking the link or visiting the page. If the payload is stored (e.g., in a product listing or custom field), it persists and affects every visitor, amplifying impact. No special tools or technical skill are necessary; proof-of-concept payloads are trivial to construct. Public disclosure or vulnerability details will likely accelerate weaponization.
Remediation
Immediately update WooCommerce Product Table Lite to the patched version released after 4.6.3. Verify the update is available through the WordPress plugin repository or the vendor's official channel. Until patching is complete, disable the plugin if it is not essential to operations. Apply input validation and output encoding best practices across all custom WooCommerce code to mitigate similar risks. Consider implementing a Web Application Firewall (WAF) with XSS filtering rules as a temporary compensating control.
Patch guidance
Check the official WooCommerce Product Table Lite plugin page in the WordPress.org repository for the latest version number and release notes. Download and install the update through the WordPress admin dashboard (Plugins > Installed Plugins > Update). Test the update in a staging environment first to confirm compatibility with your theme and other active plugins. Verify that product tables render correctly and that no functionality is broken. Document the patch date and version in your change log for compliance and audit purposes.
Detection guidance
Monitor web server and WAF logs for XSS-pattern strings in URL parameters, POST data, and HTTP headers—look for script tags, event handlers (onerror, onload), and JavaScript protocol prefixes. Review WooCommerce database tables for unexpected JavaScript in product descriptions, short descriptions, or custom fields. Use WordPress security plugins (e.g., Wordfence, Sucuri) to scan for malicious payloads and backdoors. Check browser console errors and network traffic for unexpected external script loads. Enable WordPress debug logging to catch unusual queries or plugin behavior.
Why prioritize this
This vulnerability merits immediate priority due to its network-exploitable nature, low attack complexity, and high CVSS score. The lack of authentication requirement and broad potential impact on customer data elevate it above lower-severity flaws. E-commerce sites handle payment and personal information, making XSS breaches especially damaging. The popularity of WooCommerce means attackers have significant incentive to weaponize exploits. While not yet on the CISA KEV catalog, the high severity and ease of exploitation suggest rapid adoption by threat actors if not addressed quickly.
Risk score, explained
The CVSS 3.1 score of 7.1 (HIGH) reflects a network-exploitable vulnerability requiring minimal attack complexity and no authentication. User interaction is required (someone must click a link or visit a page), which slightly reduces the score. However, the changed scope (ability to affect other systems and users) and the combination of confidentiality, integrity, and availability impacts justify the HIGH rating. This is a moderate-to-critical threat for e-commerce operations but not an emergency-level zero-day.
Frequently asked questions
Can this vulnerability be exploited if I have a firewall or security plugin enabled?
Security plugins and WAFs provide defense-in-depth but are not foolproof. A well-crafted XSS payload may evade signature-based rules, and WAFs must be actively tuned. The best defense is patching the vulnerable code itself. Security tools should complement, not replace, timely updates.
If I have auto-updates enabled, am I protected?
Only if auto-updates for plugins are enabled and functioning. Check your WordPress settings (Settings > General > Plugin Auto-updates) to confirm. Even with auto-updates on, verify that the patched version has been installed and that your site is running the latest release.
What data could an attacker steal through this XSS flaw?
Attackers can steal session cookies, API tokens, form data (including customer payment information if transmitted in plain JavaScript), and personal information visible in the page DOM. They can also redirect users to phishing sites or inject malware. The full scope of theft depends on what sensitive data is present in the page context.
Is there a temporary workaround if I cannot patch immediately?
Disable the plugin until a patch is available. If you must keep it active, implement strong input validation on all user-supplied data, use a WAF with XSS rules, and restrict access to admin areas. However, these are incomplete mitigations—patching is the only reliable solution.
This analysis is provided for informational purposes to support vulnerability management and risk assessment. It does not constitute legal advice, and organizations remain responsible for validating all claims against vendor advisories and their own systems. CVSS scores, affected versions, and patch information reflect source data current as of the analysis date; verify against the latest vendor guidance before implementing changes. No exploit code or weaponized proof-of-concept is provided. Organizations should test patches in non-production environments and maintain comprehensive backups before deployment. Source: NVD (public-domain), retrieved 2026-07-23. Analysis generated by SEC.co (claude-haiku-4-5).
Weaknesses (CWE)
Related vulnerabilities
- CVE-2016-20066HIGHWordPress CP Polls 1.0.8 Persistent XSS Vulnerability
- CVE-2016-20084HIGHWordPress Appointment-Booking-Calendar Unauthenticated XSS and Privilege Escalation
- CVE-2023-33999HIGHDOM-Based XSS in WP Mail Log Plugin – Analysis & Remediation
- CVE-2023-54351HIGHStored XSS in WordPress Sonaar Music Plugin 4.7 – Patch & Detection Guide
- CVE-2025-11262HIGHLink Whisper Free Stored XSS Vulnerability – Analysis & Patch Guidance
- CVE-2025-14773HIGHABB T-MAC Plus XSS Vulnerability – HIGH Risk Assessment
- CVE-2025-15654HIGHFox-themes Prague Reflected XSS Vulnerability – CVSS 7.1 (HIGH)
- CVE-2025-52759HIGHReflected XSS in UnboundStudio Accordion FAQ Plugin (Versions ≤2.2.1)