CVE-2026-10780
MediumCVSS 4.3Exploitation Probability (EPSS)
Low risk11th percentile — higher than 11% of all known CVEs
Summary
The Static Block plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to and including 2.2. The issue arises from the static_block_content() shortcode handler not verifying the post's status and the user's capabilities.
Risk Assessment
Authenticated attackers with contributor-level access and above can read the contents of arbitrary posts, including private and draft posts, posing a serious threat to data confidentiality.
Recommendation
It is recommended to update the plugin to the latest version and implement additional checks to verify post status and user permissions.
Original NVD description (English source)
The Static Block plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2.2. This is due to the static_block_content() shortcode handler retrieving a post via get_post() using an attacker-supplied 'id' attribute and outputting its post_content without verifying the post's status (private, draft, pending) or the requesting user's capability to view it. This makes it possible for authenticated attackers, with contributor-level access and above, to read the contents of arbitrary posts, including private and draft static blocks (and any other post type) created by administrators, by embedding the [static_block_content id="X"] shortcode in their own content and previewing it.