Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessSend unauthenticated REST API request
-
ExploitServer skips post-visibility check
-
ImpactRead protected excerpts, non-public content, WooCommerce coupons
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery 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 configuration is required for the core flaw: a remote unauthenticated attacker can query the plugin's REST API endpoint against default installations of Otter Blocks before 3.2.8 and receive data it should withhold, because the code treats any 'published'-status post as publicly readable without verifying actual readability. The exposure is limited in scope to manual excerpts of password-protected posts and the titles/content of non-public post types. The additional disclosure of coupon codes and their descriptions is CONDITIONAL on the site also running WooCommerce. Limiting factors: only data already stored in these specific forms is exposed (not full post bodies of password-protected posts beyond the manual excerpt, and no write/modify capability), and the site must be running an affected 3.1.1-3.2.7 version of the plugin. |
| Impact | This is a moderate, confidentiality-only information-disclosure issue rather than a top-priority emergency, and the available signals agree on that. The CVSS 3.1 base score of 5.3 (AV:N/AC:L/PR:N/UI:N, C:L/I:N/A:N) reflects an easy, remote, unauthenticated reach but only a limited confidentiality impact and no integrity or availability effect. The SSVC decision framework reinforces the modest picture: Exploitation 'none' (no observed activity), Automatable 'no', and Technical Impact 'partial', which aligns with the vuln.today 'this_month' priority label - act within the normal patch cycle, not immediately. There is no CISA KEV listing and no confirmed public exploit code, so this is not confirmed active exploitation. EPSS is NOT provided in the input, so exploitation probability cannot be quantified here - this is a genuine data gap. The CVSS 'C:L' rating matches the description: what leaks is bounded (manual excerpts of password-protected posts, titles/content of non-public post types, and - only on WooCommerce sites - coupon codes and descriptions), not full credential or database compromise. Net: a real but low-urgency flaw whose chief value to an attacker is reconnaissance or scraping of unpublished/discount data. |
| Exploit ScenarioDerived | An unauthenticated attacker sends crafted requests to the plugin's REST API endpoint on a WordPress site running Otter Blocks before 3.2.8, which incorrectly treats any post with 'published' status as public. The response leaks manual excerpts of password-protected posts, the titles and content of non-public post types, and on WooCommerce sites the coupon codes and their descriptions. No public exploit identified at time of analysis, but exploitation is scriptable given the low complexity and lack of authentication. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 23, 2026
An information disclosure flaw in the Otter Blocks WordPress plugin before 3.2.8 lets unauthenticated remote attackers retrieve data through a REST API endpoint that should not be publicly readable, because the plugin treats any post marked 'published' as public without checking actual readability. Affected sites are those running versions 3.1.1 through 3.2.7; exposed data is limited to manual excerpts of password-protected posts and titles/content of non-public post types, with WooCommerce coupon codes and descriptions additionally exposed on sites running WooCommerce. This is a moderate, confidentiality-only issue (CVSS 5.3); no public exploit code or active exploitation is identified at time of analysis, and a vendor patch is available.
RemediationAI
Vendor-released patch: Otter Blocks 3.2.8. Updating the plugin to 3.2.8 or later is the complete fix, since the corrected release performs a proper readability determination before returning post data; the vendor advisory is at https://wpscan.com/vulnerability/f634bde0-bfb0-4bf9-9c85-fb72763c5dfd/ and the plugin is normally updated through the WordPress admin Plugins screen or WP-CLI. Because this is a low-complexity, unauthenticated REST endpoint exposure with a this_month decision priority rather than an emergency, sites can schedule the update in the current patch cycle, but the practical exposure can be reduced in the interim by removing or deactivating the Otter Blocks plugin where its blocks are not in use, or by restricting access to the plugin's REST routes at the web server or application firewall level - accepting that blocking the shared /wp-json/ path can break other REST consumers such as the block editor and should be scoped to the plugin's specific route and tested before enforcement. Site operators should also confirm whether WooCommerce is installed, since that condition widens the disclosure to coupon codes and descriptions.
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 flaw is a CWE-200 information-exposure problem rooted in an authorization/visibility check that relies on post status alone rather than evaluating whether the requesting user may actually read the post. WordPress stores posts with statuses such as 'publish', 'private', and password-protected variants; the plugin's REST API endpoint returned data for any post whose status was 'published', conflating status with public readability. Consequences include disclosure of manual excerpts of password-protected posts, titles and content of non-public post types, and - only where WooCommerce is also installed - coupon codes and their descriptions, since WooCommerce stores coupons as a custom post type. The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) confirms a remotely reachable, unauthenticated, no-interaction path with confidentiality-only impact; no integrity or availability effect and no scope change. Note that status-based validation errors of this kind can recur wherever the endpoint's data objects are extended to new post types, which is why relying on the plugin's corrected readability determination is preferable to site-level whitelisting.
Know when WordPress 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
REST endpoint is reachable network-wide with no auth or interaction and a simple request (AV:N/AC:L/PR:N/UI:N); only limited data leaks (C:L), with no integrity or availability impact.
Primary rating from Vendor (wpscan).
CVSS VectorVendor: wpscan
Lifecycle Timeline
4DescriptionCVE.org
The Otter Blocks WordPress plugin before 3.2.8 does not correctly determine whether a post is publicly readable before returning its data through a REST API endpoint, treating any post with the published status as public, allowing unauthenticated users to read manual excerpts of password-protected posts, the content and titles of non-public post types, and, on WooCommerce sites, coupon codes and their descriptions.
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
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
The mailSend function in the isMail transport in PHPMailer before 5.2.18 might allow remote attackers to pass extra para
The isMail transport in PHPMailer before 5.2.20 might allow remote attackers to pass extra parameters to the mail comman
The 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 GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
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
Remote code execution in WordPress 6.9.x (before 6.9.5) and 7.0.x (before 7.0.2) arises from a REST API batch endpoint r
EUVD-2026-108587
GHSA-v2v8-j877-jpr5
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB