Home

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.

PUBLISHED Reserved 2026-06-03 | Published 2026-06-16 | Updated 2026-06-16 | Assigner Wordfence




MEDIUM: 4.3CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Problem types

CWE-639 Authorization Bypass Through User-Controlled Key

Product status

Default status
unaffected

Any version
affected

Timeline

2026-06-15:Disclosed

Credits

Yong Jin Lim finder

References

www.wordfence.com/...-cf9e-44e7-9495-686ace1ead21?source=cve

plugins.trac.wordpress.org/...c-block/trunk/static-block.php

plugins.trac.wordpress.org/...c-block/trunk/static-block.php

plugins.trac.wordpress.org/...c-block/trunk/static-block.php

cve.org (CVE-2026-10780)

nvd.nist.gov (CVE-2026-10780)

Download JSON