Skip to main content
Vulnerability Database/CVE-2026-97268

CVE-2026-97268: Premmerce Wishlist XSS Vulnerability

CVE-2026-97268 is an unauthenticated cross-site scripting flaw in Premmerce Wishlist for WooCommerce affecting versions up to 1.1.13. This post covers technical details, affected versions, security impact, 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-2026-97268 Overview

CVE-2026-97268 is an unauthenticated Cross-Site Scripting (XSS) vulnerability affecting the Premmerce Wishlist for WooCommerce WordPress plugin in versions 1.1.13 and earlier. The flaw is classified under CWE-79 (Improper Neutralization of Input During Web Page Generation).

An unauthenticated attacker can craft a malicious link or input that, when processed by the plugin, executes arbitrary JavaScript in the context of a victim's browser session. The vulnerability requires user interaction and can impact session integrity, user data, and administrative functions when triggered against logged-in users.

Critical Impact

Unauthenticated attackers can inject arbitrary JavaScript into WooCommerce storefronts running vulnerable versions, enabling session theft, credential harvesting, and administrative account compromise through victim interaction.

Affected Products

  • Premmerce Wishlist for WooCommerce plugin versions <= 1.1.13
  • WordPress sites running WooCommerce with the affected plugin installed
  • All site visitors and administrators interacting with vulnerable wishlist pages

Discovery Timeline

  • 2026-10-01 - CVE-2026-97268 published to the National Vulnerability Database
  • 2026-10-01 - Last updated in NVD database

Technical Details for CVE-2026-97268

Vulnerability Analysis

The vulnerability resides in the Premmerce Wishlist for WooCommerce plugin, which extends WooCommerce storefronts with wishlist functionality. The plugin fails to properly neutralize user-supplied input before rendering it within HTML output, allowing injection of attacker-controlled script content.

Because the issue is exploitable without authentication, any visitor to a vulnerable storefront can be used as an attack vector. Successful exploitation executes JavaScript in the victim's browser under the origin of the WordPress site, bypassing same-origin protections.

Root Cause

The root cause is improper neutralization of input during web page generation [CWE-79]. The plugin accepts input data and reflects or stores it in HTML responses without applying context-appropriate output encoding or sanitization through WordPress functions such as esc_html(), esc_attr(), or wp_kses().

The scope-changing nature of the issue indicates that injected script can affect resources beyond the originally vulnerable component, including the broader WordPress administrative interface when triggered by privileged users.

Attack Vector

Exploitation occurs over the network and requires user interaction, typically through a crafted URL delivered via phishing, forum posts, or compromised third-party sites. When a victim loads the malicious URL on a site running the vulnerable plugin, the injected payload executes within their browser session.

Attackers can leverage this to perform actions such as stealing authentication cookies, forging requests to administrative endpoints, redirecting users to attacker-controlled sites, or injecting malicious content into the storefront experience. No code examples are published for this CVE; refer to the Patchstack advisory for technical specifics.

Detection Methods for CVE-2026-97268

Indicators of Compromise

  • Web server access logs containing requests with URL-encoded <script> tags, javascript: URIs, or event handler attributes targeting wishlist endpoints
  • Unexpected outbound requests from site visitors' browsers to unknown domains following wishlist page access
  • WordPress administrator session anomalies, including logins from unusual IP addresses or new administrative accounts
  • Modified theme files, plugins, or WordPress options following suspicious wishlist page activity

Detection Strategies

  • Deploy a Web Application Firewall (WAF) with signatures tuned to detect reflected XSS payloads targeting WordPress plugin parameters
  • Review WooCommerce and WordPress audit logs for parameter values containing HTML or JavaScript syntax
  • Compare installed plugin versions against the vulnerable range <= 1.1.13 using WP-CLI or plugin inventory tooling

Monitoring Recommendations

  • Enable Content Security Policy (CSP) headers and monitor CSP violation reports for unexpected script sources
  • Alert on creation of new WordPress administrator accounts or changes to existing privileged user roles
  • Monitor outbound DNS queries from browsers accessing storefronts for connections to known malicious infrastructure

How to Mitigate CVE-2026-97268

Immediate Actions Required

  • Identify all WordPress installations running Premmerce Wishlist for WooCommerce and determine installed versions
  • Update the plugin to a version later than 1.1.13 as soon as a patched release is available from the vendor
  • If a patched version is unavailable, deactivate and remove the plugin until a fix is published
  • Force password resets for WordPress administrators who may have interacted with crafted wishlist URLs

Patch Information

Consult the Patchstack advisory for Premmerce Wishlist for WooCommerce for current patch status and remediation guidance. Site operators should subscribe to vendor update notifications and apply plugin updates through the WordPress administrative interface or WP-CLI.

Workarounds

  • Deploy a virtual patch through a WAF solution that blocks requests containing XSS payloads targeting the plugin's parameters
  • Enforce a restrictive Content Security Policy that disallows inline scripts and limits script sources to trusted origins
  • Restrict administrative access to WordPress through IP allowlisting or VPN requirements to reduce the impact of session hijacking
bash
# Example WP-CLI commands to inventory and remove the vulnerable plugin
wp plugin list --name=premmerce-woocommerce-wishlist --fields=name,status,version
wp plugin deactivate premmerce-woocommerce-wishlist
wp plugin uninstall premmerce-woocommerce-wishlist

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.