CVE-2026-10780
The Static Block plugin for WordPress is vulnerable to Insecure …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- plugins.trac.wordpress.org/browser/static-block/trunk/static-block.php#L244
- plugins.trac.wordpress.org/browser/static-block/trunk/static-block.php#L268
- plugins.trac.wordpress.org/browser/static-block/trunk/static-block.php#L270
- www.wordfence.com/threat-intel/vulnerabilities/id/f88c00ca-cf9e-44e7-9495-686ace1ead21?sou
- nvd.nist.gov/vuln/detail/CVE-2026-10780
- cve.org/CVERecord?id=CVE-2026-10780
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.