TI WooCommerce Wishlist CVE-2025-9207
MEDIUMAttack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessSend crafted request to wishlist endpoint
-
ExploitSupply malicious HTML in hidden fields
-
ExecutionPlugin stores unvalidated input
-
ImpactInjected HTML rendered to viewing users
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Input validation, allowlisting
|
| Exploitation Conditions | Exploitation requires that the TI WooCommerce Wishlist plugin (any version through 2.10.0) be installed and active on a WordPress/WooCommerce site with wishlist functionality reachable by unauthenticated visitors - the default state for a storefront. The specific vector is the plugin accepting arbitrary hidden-field values on wishlist item submission and later outputting them without validation, so no special non-default configuration is needed. Limiting factors: impact is confined to HTML markup injection (not confirmed script execution per the vendor), the injected content only takes effect when a user subsequently views the affected wishlist item, and sites already updated past 2.10.0 are not affected. |
| Impact | This is a genuinely low-to-moderate priority issue despite the unauthenticated network vector. The CVSS 3.1 score of 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N) correctly reflects a single limited impact: integrity-only (I:L) with no confidentiality or availability consequence, because the flaw permits HTML injection into wishlist items rather than script execution or data access. The EPSS score of 0.42% (34th percentile) is low, indicating no significant observed or predicted exploitation activity. The vulnerability is NOT in CISA KEV and no public exploit code is referenced, so there is no evidence of active exploitation. The one signal elevating attention is the unauthenticated nature (PR:N) combined with the plugin's sizable WordPress install base. Note a nuance: the CVSS caps impact at I:L and marks scope unchanged (S:U), but HTML injection into content later rendered to other users can, depending on output context and sanitization elsewhere, approach stored-XSS-like effects - the vendor scored this conservatively as HTML injection only, so treat the real impact as content/markup manipulation rather than confirmed script execution unless further analysis proves otherwise. Overall: a real but low-severity hygiene fix, not an emergency. |
| Exploit ScenarioDerived | An unauthenticated attacker submits a crafted request to the wishlist functionality, supplying hidden-field values containing arbitrary HTML that the plugin stores and later renders in wishlist items without adequate validation. When a victim (shopper or administrator) views the affected wishlist, the injected HTML is rendered in their browser, enabling defacement, misleading content, or phishing lures embedded in the trusted store page. No public exploit code is referenced, and exploitation requires no authentication or user interaction to inject the payload. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 07, 2026
HTML injection in the TI WooCommerce Wishlist plugin for WordPress (all versions up to and including 2.10.0) lets unauthenticated remote attackers submit arbitrary HTML through hidden wishlist-item fields that the plugin stores and later renders without validation, corrupting or spoofing wishlist content when a victim views the affected item. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms no authentication or user interaction is required to inject, though impact is limited to integrity (C:N/I:L/A:N) because the vendor scope is markup injection rather than confirmed script execution. EPSS is low at 0.42% and no public exploit code or CISA KEV entry was identified at time of analysis, making this a low-to-moderate priority issue despite the unauthenticated network vector.
RemediationAI
Update the TI WooCommerce Wishlist plugin to a release newer than 2.10.0; the upstream changeset at https://plugins.trac.wordpress.org/changeset?old=3399224%40ti-woocommerce-wishlist&new=3399224%40ti-woocommerce-wishlist indicates the fix was committed upstream, so patched versions should be applied from the official WordPress plugin repository and the exact patched tag should be confirmed on the vendor changelog (upstream fix available via commit/changeset; released patched version not independently confirmed). Consult the Wordfence advisory (https://www.wordfence.com/threat-intel/vulnerabilities/id/8d08d381-d0ef-4f40-975d-51e919a7c872?source=cve) for the latest affected-range and fix details. If immediate upgrade is not possible, remove the plugin, or if wishlist functionality is required, restrict public wishlist access using the plugin's own settings and front-end access controls and consider a WAF rule blocking hidden-field parameters on wishlist submission - noting that WAF rules may have false positives and do not address already-stored malicious content, and that restricting wishlist reachability reduces the attack surface but degrades the storefront's social/sharing features.
Affected ProductsAI
TI WooCommerce Wishlist plugin for WordPress, all versions up to and including 2.10.0, on sites where the plugin is installed, active, and its wishlist functionality is reachable by unauthenticated visitors. The relevant code paths are in includes/wishlist.class.php as cited in the NVD references (plugin Trac source lines 326 and 544) and the plugin changeset at https://plugins.trac.wordpress.org/changeset?old=3399224%40ti-woocommerce-wishlist&new=3399224%40ti-woocommerce-wishlist. Wordfence tracks the issue at https://www.wordfence.com/threat-intel/vulnerabilities/id/8d08d381-d0ef-4f40-975d-51e919a7c872?source=cve. Sites already running a version newer than 2.10.0 are not affected.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected component is the WordPress plugin TI WooCommerce Wishlist, which extends WooCommerce storefronts with shareable wishlist functionality. Root cause is CWE-20 (Improper Input Validation): the plugin accepts hidden form fields on wishlist item submission and does not constrain the values or data type, then outputs those stored values into the page without sanitization, as evidenced by the referenced source lines in includes/wishlist.class.php (lines 326 and 544) where wishlist data is handled. This is a stored/persistent HTML injection rather than a classic reflected XSS; the injected markup only renders when a user subsequently views the affected wishlist item, which narrows the practical exposure. No CPE strings were supplied, but the affected artifact is the WordPress plugin slug ti-woocommerce-wishlist.
Know when Wordpress Plugin gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Unauthenticated remote submission (AV:N/AC:L/PR:N/UI:N) with integrity-only impact from HTML injection into stored items (I:L); no confidentiality or availability effect and scope unchanged.
Primary rating from Vendor (wordfence).
CVSS VectorVendor: wordfence
DescriptionCVE.org
The TI WooCommerce Wishlist plugin for WordPress is vulnerable to HTML Injection in all versions up to, and including, 2.10.0. This is due to the plugin accepting hidden fields and not limiting the values or data that can input and is later output. This makes it possible for unauthenticated attackers to inject arbitrary HTML into wishlist items.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB