Skip to main content

CVE-2025-5238: YITH WooCommerce Wishlist XSS Vulnerability

CVE-2025-5238 is a stored XSS vulnerability in YITH WooCommerce Wishlist plugin for WordPress that allows authenticated attackers to inject malicious scripts. This post explains its impact, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2025-5238 Overview

CVE-2025-5238 is a Stored Cross-Site Scripting (XSS) vulnerability in the YITH WooCommerce Wishlist plugin for WordPress. The flaw affects all versions up to and including 4.5.0 and stems from insufficient input sanitization and output escaping of the id parameter. Authenticated attackers with Contributor-level access or higher can inject arbitrary JavaScript into pages. The injected script executes in the browser of any user who views the affected page, including administrators. The weakness is classified as CWE-79 (Improper Neutralization of Input During Web Page Generation).

Critical Impact

Authenticated contributors can plant persistent JavaScript payloads that run against site visitors and administrators, enabling session theft, account takeover, and WordPress admin compromise.

Affected Products

  • YITH WooCommerce Wishlist plugin for WordPress — all versions up to and including 4.5.0
  • WordPress sites running WooCommerce with the vulnerable plugin enabled
  • Any environment granting Contributor-level accounts or above to untrusted users

Discovery Timeline

  • 2025-06-14 - CVE-2025-5238 published to the National Vulnerability Database (NVD)
  • 2026-06-17 - Record last modified in NVD

Technical Details for CVE-2025-5238

Vulnerability Analysis

The YITH WooCommerce Wishlist plugin accepts an id parameter that is rendered back into page output without adequate sanitization or escaping. Because the value is persisted and later reflected in rendered HTML, any script payload supplied by an authenticated low-privileged user is stored and executed on subsequent page loads. The vulnerability requires authentication at the Contributor level or above, which lowers exploitation friction on multi-author WordPress sites, membership portals, and e-commerce stores that onboard external sellers or writers. Successful exploitation can lead to administrator session hijacking, forced actions via the admin interface, and plugin or theme modification, which can escalate into full site takeover.

Root Cause

The root cause is missing input validation on the id parameter combined with absent output escaping when the stored value is rendered in the page document. WordPress provides escaping helpers such as esc_attr(), esc_html(), and wp_kses() that the plugin should apply at the output boundary. Without them, attacker-controlled markup is emitted directly into the Document Object Model (DOM).

Attack Vector

An authenticated contributor sends a crafted request containing a malicious payload in the id parameter handled by the wishlist plugin. The payload is persisted server-side and included in the HTML of pages that reference the wishlist. When a victim — typically an authenticated administrator or editor — loads the page, the browser executes the attacker's JavaScript in the site's origin. See the Wordfence Vulnerability Analysis and the fix in WordPress Trac Changeset #3310555 for the affected code paths. No verified public exploit code is referenced in the advisory.

Detection Methods for CVE-2025-5238

Indicators of Compromise

  • Wishlist records or post metadata containing HTML tags such as <script>, <svg onload=...>, or javascript: URIs in the id field
  • Unexpected outbound requests from browsers after rendering wishlist pages, especially to attacker-controlled domains
  • New or modified WordPress administrator accounts following access by a privileged user to wishlist pages
  • Contributor accounts posting or editing wishlist-related content outside normal patterns

Detection Strategies

  • Review HTTP request logs for POST and GET traffic to wishlist endpoints that include angle brackets or encoded script fragments in the id parameter
  • Inspect the WordPress database — including the wp_postmeta and plugin-specific tables — for stored values containing HTML or JavaScript
  • Compare the installed plugin version against the fixed release noted in the YITH WooCommerce Wishlist Changelog

Monitoring Recommendations

  • Enable Web Application Firewall (WAF) rules that identify XSS payloads targeting WordPress plugin parameters
  • Alert on creation of new administrator roles, changes to wp_users, and modifications to plugin or theme files
  • Monitor Content Security Policy (CSP) violation reports for unexpected inline script execution on WooCommerce pages

How to Mitigate CVE-2025-5238

Immediate Actions Required

  • Update the YITH WooCommerce Wishlist plugin to a version later than 4.5.0 that includes the fix referenced in WordPress Trac Changeset #3310555
  • Audit Contributor-level and higher accounts, remove unused or suspicious users, and enforce strong authentication
  • Review wishlist content and post metadata for existing stored payloads and purge any malicious entries
  • Rotate administrator session cookies and credentials if indicators of compromise are present

Patch Information

The vendor addressed the vulnerability in a release following 4.5.0. Refer to the YITH WooCommerce Wishlist Changelog for the fixed version and to the Wordfence Vulnerability Analysis for additional remediation detail. The patch introduces proper sanitization and output escaping around the id parameter.

Workarounds

  • Temporarily restrict wishlist functionality or disable the plugin until the patch is applied
  • Limit account creation and demote Contributor-level users on sites that do not require guest authoring
  • Deploy a WAF rule that blocks requests containing script tags or event-handler attributes targeting wishlist endpoints
  • Enforce a strict Content Security Policy that disallows inline scripts on WooCommerce storefront pages
bash
# Example: update the plugin using WP-CLI once a fixed release is published
wp plugin update yith-woocommerce-wishlist
wp plugin list --name=yith-woocommerce-wishlist --fields=name,status,version

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.