CVE-2026-10780
No known patch is available for this vulnerability.
The affected plugin has been removed from the WordPress.org directory, and no patched version is being distributed through the official directory. If you have the affected software installed, you should uninstall or replace it rather than wait for an update.
Description
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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected products
2<=2.2+ 1 more
- (no CPE)range: <=2.2
- (no CPE)range: <=2.2
Patches
Vulnerability mechanics
References
4- plugins.trac.wordpress.org/browser/static-block/trunk/static-block.phpnvd
- plugins.trac.wordpress.org/browser/static-block/trunk/static-block.phpnvd
- plugins.trac.wordpress.org/browser/static-block/trunk/static-block.phpnvd
- www.wordfence.com/threat-intel/vulnerabilities/id/f88c00ca-cf9e-44e7-9495-686ace1ead21nvd
News mentions
1- Wordfence Intelligence Weekly WordPress Vulnerability Report (June 15, 2026 to June 21, 2026)Wordfence Blog · Jun 25, 2026