Skip to main content

WC Return Products CVE-2025-59004

HIGH
Cross-site Scripting (XSS) (CWE-79)
2025-10-22 audit@patchstack.com
7.1
CVSS 3.1 · Vendor: patchstack
Share

Severity by source

Vendor (patchstack) PRIMARY
7.1 HIGH
AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
vuln.today AI
6.1 MEDIUM

Reflected XSS is network-reachable with no attacker privileges (PR:N) but needs victim click (UI:R); script runs cross-context (S:C) with Low C/I and no realistic availability impact (A:N).

3.1 AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N

Primary rating from Vendor (patchstack).

CVSS VectorVendor: patchstack

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

Lifecycle Timeline

3
Metadata Corrected
Oct 08, 2026 - 12:40 vuln.today
tag: Woocommerce added
Analysis Generated
Oct 08, 2026 - 12:31 vuln.today
CVE Published
Oct 22, 2025 - 15:15 cve.org
HIGH 7.1

DescriptionCVE.org

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in pco_58 WC Return products wc-return-product allows Reflected XSS.This issue affects WC Return products: from n/a through <= 1.5.

AnalysisAI

Reflected cross-site scripting in the WC Return products WordPress plugin (all versions up to and including 1.5) allows remote attackers to execute arbitrary script in a victim's browser session by luring that victim to a crafted URL whose input is reflected unsanitized into a page the plugin generates. Per the authoritative assessment (CVSS 7.1, CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N), no attacker-side authentication is required (PR:N) but exploitation hinges on victim interaction (UI:R), so the attacker cannot trigger execution autonomously and impact is bounded by the clicking victim's session privileges. Only sites with the plugin installed and active are reachable via this code path; EPSS is low (0.25%, 15th percentile), the flaw is not listed in CISA KEV, and no public exploit code has been identified at time of analysis.

Technical ContextAI

This is a classic CWE-79 improper neutralization of input during web page generation - specifically a reflected XSS pattern - in a WordPress plugin that extends WooCommerce with return/RMA functionality. The plugin accepts attacker-controllable input (typically a query-string or request parameter) and writes it back into the HTML response without output encoding or sanitization, so the browser parses injected markup and script as part of the page. The assessed vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N indicates the attack is delivered over the network, needs no privileges to craft but requires the victim to click a specially crafted link, and crosses a security scope boundary (S:C) because the injected script runs in the context of the vulnerable WordPress site and can therefore reach the victim's authenticated session, cookies, or CSRF-capable endpoints on that origin. CPE data is not supplied in the available intelligence, but the affected artifact is unambiguously the WordPress plugin slug wc-return-product (vendor pco_58) at version 1.5 and earlier; the vulnerable code path is only reachable on WordPress installations where the plugin is installed and active, and its practical value to an attacker is highest on sites where an administrator or shop manager can be socially engineered into clicking the link.

Affected ProductsAI

The affected product is the WC Return products plugin for WordPress, published by pco_58 under the slug wc-return-product, across all versions from n/a through 1.5 inclusive (i.e., 1.5 is the highest vulnerable release listed). Because the plugin augments WooCommerce storefronts, the realistic exposure set is WordPress sites running WooCommerce that have this plugin installed and activated; sites where the plugin is installed but inactive are not reachable via this code path. No CPE strings were provided in the supplied intelligence feed, so version matching should be performed against the plugin's own version header/slug rather than a CPE dictionary. The vendor-facing reference is the Patchstack advisory at https://patchstack.com/database/Wordpress/Plugin/wc-return-product/vulnerability/wordpress-wc-return-products-plugin-1-5-reflected-cross-site-scripting-xss-vulnerability?_s_id=cve, which documents the reflected XSS in the 1.5 release.

RemediationAI

Patch status is not confirmed by the available data: no fixed version is named in the supplied references, and the only advisory link (the Patchstack entry for wc-return-product 1.5) documents the issue rather than an upgrade target, so administrators should check the plugin's WordPress.org page and the Patchstack advisory directly for a newly released version before assuming a fix exists. Until a vendor-released version above 1.5 is verified, the most effective action is to deactivate and delete the WC Return products plugin if the store does not depend on it - this removes the vulnerable code path entirely and carries only the trade-off of losing the return/RMA feature. If the functionality is business-critical, the plugin must stay enabled, so treat the reflected XSS as an accepted, managed risk and layer compensating controls: deploy a WAF or reverse-proxy rule that inspects and blocks script-bearing markup in query parameters and request bodies targeting plugin endpoints (side effect: possible false positives on legitimate input and ongoing rule maintenance); enforce a strict Content-Security-Policy on the WordPress origin that disallows inline and third-party scripts (side effect: may break themes or other plugins that rely on inline JavaScript); set HttpOnly and SameSite=Lax/Strict on session cookies to reduce cookie theft from injected script (side effect: may affect cross-site workflows); and require any user who might be targeted - especially administrators and shop managers - to keep sessions short and resist clicking unsolicited links. Monitor the Patchstack advisory and the plugin changelog for a fixed release and upgrade as soon as one is published.

CVE-2017-17058 HIGH POC
7.5 Nov 29

The WooCommerce plugin through 3.x for WordPress has a Directory Traversal Vulnerability via a /wp-content/plugins/wooco

CVE-2021-24212 CRITICAL POC
9.8 Apr 05

The WooCommerce Help Scout WordPress plugin before 2.9.1 (https://woocommerce.com/products/woocommerce-help-scout/) allo

CVE-2022-50972 CRITICAL POC
9.3 Jun 20

WooCommerce 7.1.0 contains a remote code execution vulnerability that allows attackers to execute arbitrary PHP code by

CVE-2020-35627 HIGH POC
8.8 Dec 28

Ultimate WooCommerce Gift Cards 3.0.2 is affected by a file upload vulnerability in the Custom GiftCard Template that ca

CVE-2026-14962 HIGH POC
8.6 Sep 09

Unauthenticated SQL injection in the ELEX WooCommerce Request a Quote WordPress plugin (all versions before 2.4.1) allow

CVE-2026-92404 HIGH POC
7.5 Sep 19

Unauthenticated, network-reachable attackers can read the WooCommerce API consumer key and secret stored by the MgoSync

CVE-2023-34000 HIGH POC
7.5 Jun 14

Unauth. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low atta

CVE-2020-11497 HIGH POC
7.5 Aug 26

An issue was discovered in the NAB Transact extension 2.1.0 for the WooCommerce plugin for WordPress. Rated high severit

CVE-2026-74925 HIGH POC
7.2 Sep 11

Privilege escalation in MultiVendorX WordPress plugin before 5.0.16 allows authenticated vendor-role users to grant admi

CVE-2023-47777 MEDIUM POC
6.5 Nov 30

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Automattic WooComm

CVE-2026-103378 MEDIUM POC
6.5 Oct 07

Unauthenticated information disclosure in the Geliver Akıllı Kargo Pazaryeri WordPress plugin (versions 3.0.0 through 3.

CVE-2026-93509 MEDIUM POC
6.5 Oct 08

Authenticated attackers with only Subscriber-level access can mint wallet funds for themselves or drain a specific victi

Share

CVE-2025-59004 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy