Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach WordPress REST API endpoint
-
ExploitRequest private wishlist by ID
-
ExecutionAPI skips owner-only check
-
ImpactRead leaked wishlist metadata and items
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Access control enforcement
MITRE ATT&CK
1 technique across 1 tactic: Defense Evasion The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | No authentication, user interaction, or special privilege is required - exploitation works against a default installation of TI WooCommerce Wishlist (versions before 2.13.0) simply by querying its REST API endpoints directly instead of the front-end. The specific prerequisite is that the target site runs the vulnerable plugin version and that the attacker can reference private wishlists (e.g., by their identifiers); the only real limit on impact is that exposure is confined to wishlist metadata and item contents, not broader site or user-credential data. No non-default configuration is needed to trigger the flaw. |
| Impact | All signals describe a broken-access-control information-disclosure flaw (CWE-284) of moderate severity. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N = 5.3 Medium) is internally consistent with the description: the REST API is reachable remotely by unauthenticated users with no interaction, but impact is limited to confidentiality (C:L) with no integrity or availability effect - it only leaks private wishlist metadata and item contents, not credentials or system data. Publicly available exploit code exists (reported by WPScan), which raises practical exploitability, but this vulnerability is NOT in CISA KEV and no EPSS score was provided in the input, so there is no confirmation of active, widespread exploitation. The realistic picture is a genuine, easily-triggered privacy/data-exposure bug rather than a system-compromise emergency: low technical impact caps the ceiling. Note a conflict to verify: the input Tags label this 'Authentication Bypass,' but the description and CWE-284 indicate an authorization (owner-only access control) failure on the REST API, not an authentication bypass - the distinction matters for triage. EPSS and SSVC data were not supplied, so automatability and exploitation-likelihood scoring could not be incorporated. |
| Exploit ScenarioDerived | An unauthenticated attacker enumerates or guesses wishlist identifiers and sends direct requests to the plugin's REST API endpoints, which - unlike the front-end - fail to enforce the owner-only check. The API returns the metadata and item contents of other users' private wishlists, exposing their saved products and associated data. Publicly available exploit code (WPScan) lowers the skill barrier to carry this out at scale. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
Broken access control in the TI WooCommerce Wishlist WordPress plugin before 2.13.0 lets unauthenticated remote attackers read the metadata and item contents of private wishlists by querying the plugin's REST API directly, bypassing the owner-only checks enforced on the front-end. No account, privilege, or user interaction is needed - only a vulnerable installation and a way to reference the target wishlist identifiers - and exposure is limited to wishlist metadata and contents rather than broader site or credential data. Publicly available exploit code exists for this CWE-284 flaw (CVSS 5.3, unauthenticated), though it is not confirmed as actively exploited in the wild.
RemediationAI
Update the TI WooCommerce Wishlist plugin to version 2.13.0 or later - the vendor-released fixed version - through the WordPress plugin updater or by deploying the tagged release from the vendor; the advisory is at https://wpscan.com/vulnerability/64e9f028-2124-4800-a5cf-0ed5d4d13e62/. If immediate patching is not possible, compensate by blocking unauthenticated access to the plugin's REST API routes at the WAF or reverse-proxy layer (deny requests to the plugin's namespace under /wp-json/ for anonymous clients) - the trade-off is that legitimate logged-out wishlist or share-link functionality that depends on those routes will break, so validate the rule against expected site behavior first. Alternatively, temporarily deactivate the plugin until it can be updated, accepting the loss of wishlist features. Because the CPE identifies the vendor as 'unknown', do not depend on CPE-based scanning to confirm exposure; audit installed plugin versions directly, and expect any site that has not yet run the 2.13.0 update to remain affected.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
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 a WordPress plugin that exposes wishlist functionality through both rendered front-end views and WordPress REST API routes. The plugin correctly applies owner-only authorization checks to front-end wishlist access, but the corresponding REST API handlers do not replicate that check, so requests to the API endpoints skip the ownership validation entirely. This is a classic improper access control (CWE-284) pattern: authorization logic implemented in one presentation layer rather than in the shared data-access layer, leaving a parallel interface unprotected. Because WordPress REST routes are reachable over the network without authentication by default (CVSS:3.1/AV:N/AC:L/PR:N/UI:N), any party able to enumerate or guess wishlist identifiers can retrieve private wishlist metadata and item contents. The CPE entry records the vendor as 'unknown' (cpe:2.3:a:unknown:ti_woocommerce_wishlist:*:*:*:*:*:*:*:*), so coverage in CPE-driven scanners should not be relied upon - version verification must be done directly against the installed plugin version.
Know when Ti Woocommerce Wishlist 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:L/I:N/A:N
Remote unauthenticated REST API access with no interaction (AV:N/AC:L/PR:N/UI:N); only private wishlist data is disclosed, so C:L with no integrity or availability impact.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
4DescriptionCVE.org
The TI WooCommerce Wishlist WordPress plugin before 2.13.0 does not enforce the same owner-only access control on its REST API that it applies on the front-end, allowing unauthenticated users to read the metadata and item contents of private wishlists.
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
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
More in Ti Woocommerce Wishlist
View allImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in TemplateInvaders T
The TI WooCommerce Wishlist WordPress plugin before 1.40.1, TI WooCommerce Wishlist Pro WordPress plugin before 1.40.1 d
The TI WooCommerce Wishlist and TI WooCommerce Wishlist Pro plugins for WordPress are vulnerable to an Options Change vu
The TI WooCommerce Wishlist WordPress plugin through 2.8.2 is vulnerable to SQL Injection due to insufficient escaping o
EUVD-2026-107080
GHSA-84p5-6x2c-h74j
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB