WPC Frequently Bought Together for WooCommerce unauthenticated stored XSS via variation parameter
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
The WPC Frequently Bought Together for WooCommerce plugin from wpclever has a stored cross-site scripting flaw in its 'variation' parameter. An attacker can reach it remotely, without logging in, and inject arbitrary web scripts into pages, which then run whenever a user opens an affected page.
Written by a model
Original description
The WPC Frequently Bought Together for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'variation' parameter in all versions up to, and including, 8.0.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The nonce protecting the woobt_add_all_to_cart AJAX handler is emitted to all unauthenticated visitors via wp_localize_script, effectively nullifying the nonce as an authentication barrier and making the handler reachable without any login.
Who should check
Sites running the WPC Frequently Bought Together for WooCommerce plugin (wpclever) version 8.0.2 or earlier on WooCommerce stores
“Fixed: Stored XSS vulnerability via unsanitized variation attributes”
What to do
Workaround: The checked facts give no workaround or mitigation for this issue. Until a fixed version is confirmed, the facts do not support any specific step beyond checking the plugin version.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133367 (WPC Frequently Bought Together for WooCommerce <= 8.0.2 - Unauthenticated Stored Cross-Site Scripting via 'variation' Parameter), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133367 (entry last updated 2026-11-21):
Affected:
- wpclever WPC Frequently Bought Together for WooCommerce: through 8.0.2
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- WPC Frequently Bought Together for WooCommerce plugin version 8.0.2 or earlier (source: https://wordpress.org/plugins/woo-bought-together/)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-133367 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133367 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/08e4c3a3-040f-4d2b-805c-f512bd95812d?source=cve
- https://plugins.trac.wordpress.org/browser/woo-bought-together/tags/8.0.2/includes/class-woobt.php#L67
- https://plugins.trac.wordpress.org/browser/woo-bought-together/tags/8.0.2/includes/class-woobt.php#L219
- https://plugins.trac.wordpress.org/browser/woo-bought-together/tags/8.0.2/includes/class-woobt.php#L610
- https://plugins.trac.wordpress.org/browser/woo-bought-together/tags/8.0.2/includes/class-woobt.php#L624
- https://wordpress.org/plugins/woo-bought-together/
- https://plugins.trac.wordpress.org/changeset/3813247/woo-bought-together/trunk/includes/class-woobt.php
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133367
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133367"}.Affected versions
- wpclever WPC Frequently Bought Together for WooCommercethrough 8.0.2
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.2/10CVSS 7.2
- No patch5/5No patch listed yet
What would change the score
- Would score about 74 if added to CISA KEV
- Would score about 69 if CISA's SSVC rates exploitation active
- Would score about 34 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 9
Questions about CVE-2026-133367
Is CVE-2026-133367 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
The plugin does not sanitize variation attributes, so an unauthenticated visitor can submit script through the 'variation' parameter and have it stored. The stored script can then run in the browsers of people who view the affected content.
Source: wordpress.org
Which versions are affected by CVE-2026-133367?
WPC Frequently Bought Together for WooCommerce: through 8.0.2.
Source: cve.now feed data
Am I affected, and how do I check?
All versions of WPC Frequently Bought Together for WooCommerce up to and including 8.0.2 are listed as affected. To check a site, look at the plugin version shown in the WordPress Plugins screen or the plugin header.
Source: wordpress.org
How do I fix CVE-2026-133367?
The checked facts name no fixed version and no vendor patch identifier, so this page cannot confirm an upgrade target. The vendor's changelog entry says the stored XSS was fixed, so check the plugin's changelog for the first release that includes that fix.
Source: wordpress.org
What if there's no patch?
The checked facts give no workaround or mitigation for this issue. Until a fixed version is confirmed, the facts do not support any specific step beyond checking the plugin version.
Source: wordpress.org
Related
- CVE-2024-43312WordPress WPC Frequently Bought Together for WooCommerce plugin <= 7.1.9 - Broken Access Control vulnerability
- CVE-2024-32687WordPress WPC Frequently Bought Together for WooCommerce plugin <= 7.0.3 - Broken Access Control vulnerability
- CVE-2026-95687WPC Shop as a Customer for WooCommerce <= 2.0.0 - Authenticated (Subscriber+) Privilege Escalation via Missing Role Check on Target User to wpcsa_login AJAX Endpoint
- CVE-2026-49061WordPress WPC Product Options for WooCommerce plugin <= 3.2.1 - Arbitrary File Download vulnerability
- CVE-2026-48883WordPress WPC Product Bundles for WooCommerce plugin <= 8.5.3 - Broken Access Control vulnerability
- CVE-2025-60248WordPress WPC Product Options for WooCommerce plugin <= 3.1.3 - Local File Inclusion vulnerability
No corrections so far. Something wrong on this page? Report an error.