PatchSiren cyber security CVE debrief
CVE-2026-10780 mohammadtanzilurrahman CVE debrief
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.
- Vendor
- mohammadtanzilurrahman
- Product
- Static Block
- CVSS
- MEDIUM 4.3
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-06-16
- Original CVE updated
- 2026-06-16
- Advisory published
- 2026-06-16
- Advisory updated
- 2026-06-16
Who should care
Users of the Static Block plugin for WordPress, particularly those with contributor-level access and above, should be aware of this vulnerability and take steps to mitigate it.
Technical summary
The vulnerability is caused by the static_block_content() shortcode handler's failure to verify the post's status or the requesting user's capability to view it when retrieving a post via get_post() using an attacker-supplied 'id' attribute.
Defensive priority
MEDIUM
Recommended defensive actions
- Update the Static Block plugin to a version that is not vulnerable.
- Use a Web Application Firewall (WAF) to detect and prevent attacks.
- Monitor your website for suspicious activity.
Evidence notes
The vulnerability was reported by [email protected].
Official resources
CVE-2026-10780 was published on 2026-06-16T06:16:58.013Z.