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-2024-1088 Overview
CVE-2024-1088 is an information disclosure vulnerability in the Password Protected Store for WooCommerce plugin for WordPress. The flaw affects all versions up to and including 2.2. Unauthenticated attackers can abuse the WordPress REST API to extract protected post titles and content that the plugin was intended to shield behind a password gate. The vulnerability is tracked under [CWE-284: Improper Access Control] and is documented in the Wordfence Vulnerability Report.
Critical Impact
Unauthenticated remote attackers can retrieve password-protected store content, including product titles and body text, by querying the exposed REST API endpoints.
Affected Products
- Rajkakadiya Password Protected Store for WooCommerce plugin for WordPress
- All plugin versions up to and including 2.2
- WordPress sites using the plugin to gate WooCommerce store content
Discovery Timeline
- 2024-03-05 - CVE-2024-1088 published to the National Vulnerability Database
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2024-1088
Vulnerability Analysis
The plugin restricts browser access to WooCommerce store pages behind a password prompt but fails to apply the same access controls at the REST API layer. WordPress exposes posts and custom post types through the /wp-json/wp/v2/ namespace by default. When a plugin only enforces password gating in the front-end template path, the underlying REST endpoints continue to serve the raw post data to any unauthenticated caller.
Attackers do not need credentials, user interaction, or elevated privileges to retrieve the data. The exposure is limited to confidentiality: no integrity or availability impact is involved. The current EPSS probability is 0.572%.
Root Cause
The root cause is an improper access control failure categorized as [CWE-284]. The plugin's password protection logic operates on front-end page rendering rather than on the REST API controllers that return the same post objects. Because no permission_callback or capability check gates the relevant REST routes, the password requirement is trivially bypassed by querying the API directly.
Attack Vector
The attack vector is network based and requires no authentication. An attacker enumerates WordPress REST endpoints such as /wp-json/wp/v2/posts, /wp-json/wp/v2/pages, or custom WooCommerce product endpoints on a target site running the vulnerable plugin. The API returns the titles and content of posts that are otherwise gated behind the plugin's password screen. See the Wordfence advisory for technical confirmation of the exposure path.
No public proof-of-concept exploit code is listed in the enriched references. The vulnerability mechanism is described in prose because no verified exploitation code is available.
Detection Methods for CVE-2024-1088
Indicators of Compromise
- Unauthenticated GET requests to /wp-json/wp/v2/posts, /wp-json/wp/v2/pages, or WooCommerce product REST endpoints from unexpected source IPs
- High-volume REST API enumeration against sites running the Password Protected Store for WooCommerce plugin
- Access logs showing successful 200 responses to REST calls that return post content normally hidden behind the password prompt
Detection Strategies
- Review web server access logs for wp-json requests paired with user-agent strings associated with scanners such as wpscan, curl, or scripted clients
- Compare REST API response bodies against the set of posts marked as password-protected to identify leakage
- Deploy a web application firewall rule that flags unauthenticated requests to WordPress REST endpoints returning gated post data
Monitoring Recommendations
- Centralize WordPress and web server logs for continuous review of REST API traffic patterns
- Alert on bursts of /wp-json/ requests from a single source address within short time windows
- Monitor plugin version inventories across WordPress fleets to detect installations still running version 2.2 or earlier
How to Mitigate CVE-2024-1088
Immediate Actions Required
- Update the Password Protected Store for WooCommerce plugin to a version later than 2.2 as published on the WordPress plugin page
- Audit site content to determine what information was exposed if the plugin has been running unpatched
- Restrict unauthenticated access to the WordPress REST API where business requirements allow
Patch Information
The vendor addressed the vulnerability through a plugin update tracked in the WordPress Plugin Changeset. Site operators should upgrade through the WordPress admin dashboard or by reinstalling the plugin from the official repository.
Workarounds
- Disable the plugin until the patched version can be installed if an upgrade is not immediately possible
- Use a web application firewall or .htaccess rule to deny unauthenticated requests to /wp-json/wp/v2/ endpoints returning gated content
- Mark affected posts as private within WordPress so core permission checks apply at the REST API layer
# Example Apache rule to block unauthenticated REST access to gated endpoints
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{HTTP_COOKIE} !wordpress_logged_in
RewriteRule ^wp-json/wp/v2/(posts|pages|product) - [F,L]
</IfModule>
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

