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-15261 Overview
The TI WooCommerce Wishlist plugin for WordPress contains a broken access control vulnerability in versions before 2.13.0. The plugin enforces owner-only access on its front-end interface but fails to apply the same control on its REST API endpoints. Unauthenticated attackers can query the REST API directly to read metadata and item contents of private wishlists belonging to other users. The flaw is classified under CWE-284 (Improper Access Control) and affects the confidentiality of wishlist data stored on vulnerable WordPress sites.
Critical Impact
Unauthenticated remote attackers can read the contents and metadata of private wishlists through the plugin's REST API, exposing user shopping intent and product selections.
Affected Products
- TI WooCommerce Wishlist WordPress plugin versions prior to 2.13.0
- WordPress sites running WooCommerce with the vulnerable plugin installed
- Any site exposing the plugin's REST API routes to the public internet
Discovery Timeline
- 2026-10-21 - CVE-2026-15261 published to the National Vulnerability Database (NVD)
- 2026-10-21 - Last updated in NVD database
Technical Details for CVE-2026-15261
Vulnerability Analysis
The TI WooCommerce Wishlist plugin maintains two separate interfaces for interacting with user wishlists: a front-end interface rendered through WordPress templates and a REST API exposed through WordPress's wp-json routing. The front-end interface validates that the requesting user owns the wishlist being accessed. The REST API endpoints omit this ownership check entirely.
An unauthenticated attacker can enumerate wishlist identifiers and issue direct HTTP requests to the REST API. The server returns private wishlist metadata and the full list of products stored within. This exposes customer shopping intent, product preferences, and potentially the association between wishlist identifiers and other user attributes.
Root Cause
The vulnerability stems from inconsistent authorization enforcement across code paths that access the same underlying data. The front-end request handlers call ownership validation routines before returning wishlist contents. The REST API callback handlers skip these checks and query the database directly. This design flaw matches the pattern described by CWE-284, where a resource is protected by one access path but exposed through another.
Attack Vector
Exploitation requires only network access to the target WordPress site. No authentication, user interaction, or special privileges are needed. An attacker crafts HTTP GET requests to the plugin's REST API routes and iterates through wishlist identifiers to harvest private data. The attack can be automated at scale against any site running a vulnerable plugin version.
See the WPScan Vulnerability Report for additional technical details on the affected endpoints.
Detection Methods for CVE-2026-15261
Indicators of Compromise
- Repeated unauthenticated requests to /wp-json/ routes exposed by the TI WooCommerce Wishlist plugin
- Sequential or enumerated wishlist identifier values appearing in HTTP access logs
- Unusual spikes in REST API traffic from single source IP addresses or cloud provider ranges
- Outbound responses containing wishlist payloads correlated with unauthenticated sessions
Detection Strategies
- Review WordPress and web server logs for high-volume access to the plugin's REST API namespace
- Inspect request patterns for identifier enumeration against wishlist endpoints
- Correlate anonymous REST API traffic with the installed version of the TI WooCommerce Wishlist plugin
Monitoring Recommendations
- Enable verbose logging on wp-json routes and forward logs to a centralized SIEM or data lake
- Alert on anonymous REST API access patterns that return wishlist response objects
- Track plugin version inventory across managed WordPress estates to identify unpatched instances
How to Mitigate CVE-2026-15261
Immediate Actions Required
- Upgrade the TI WooCommerce Wishlist plugin to version 2.13.0 or later on every affected WordPress site
- Audit WordPress and web server logs for prior unauthenticated access to the plugin's REST API endpoints
- Inventory all WordPress sites in the environment to confirm no vulnerable version remains installed
Patch Information
The vendor addressed the issue in TI WooCommerce Wishlist version 2.13.0. The fix extends the owner-only access control checks from the front-end code paths to the REST API callback handlers. Administrators should apply the update through the WordPress plugin updater or by replacing the plugin files with the patched release.
Workarounds
- Restrict access to the /wp-json/ namespace at the web server or Web Application Firewall (WAF) layer until patching is complete
- Deactivate the TI WooCommerce Wishlist plugin on sites that cannot be updated immediately
- Block anonymous requests to plugin-specific REST routes using rules at the reverse proxy or CDN
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

