CVE-2026-34902
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUnauthenticated Cross Site Scripting (XSS) in WooCommerce Product Table Lite <= 4.6.3 versions.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceUnauthenticated Cross Site Scripting (XSS) vulnerability in WooCommerce Product Table Lite plugin affecting versions 4.6.3 and prior. Attackers can inject malicious JavaScript payloads via unspecified input vectors without requiring authentication, potentially leading to session hijacking or credential theft.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify WooCommerce Product Table Lite is installedLog into WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'WooCommerce Product Table Lite' in the list. Alternatively, check for the plugin directory at /wp-content/plugins/woocommerce-product-table-lite/Affected if The plugin is present in the WordPress installation
-
Locate the installed version numberIn WordPress admin, find the plugin in the Installed Plugins list and view the version number displayed below the plugin name. Alternatively, open the main plugin file (usually woocommerce-product-table-lite.php) and look for the 'Version' header in the plugin comment blockAffected if A version number is displayed that can be compared
-
Compare version against affected rangeCompare your installed version to 4.6.3. If the installed version is 4.6.3 or lower (for example, 4.6.2, 4.6.1, 4.0, etc.), the installation is within the affected rangeAffected if Installed version is 4.6.3 or any version lower than 4.6.3
-
Confirm plugin is active and publicly accessibleCheck the WordPress Plugins page to verify the plugin status shows 'Active'. Since this is an unauthenticated XSS, determine if the plugin output is rendered on any public-facing pages (product pages, catalog views, or shortcode outputs)Affected if Plugin is active and visible to unauthenticated visitors on the site
The environment is affected if WooCommerce Product Table Lite is installed with version 4.6.3 or lower and the plugin is active on publicly accessible pages.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate WooCommerce Product Table Lite to the latest version beyond 4.6.3. If no patch is available, consider disabling the plugin or deploying a WAF rule to filter malicious XSS payloads.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34902 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-34902 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data