CVE-2026-10780: CWE-639 Authorization Bypass Through User-Controlled Key in mohammadtanzilurrahman Static Block
The Static Block WordPress plugin up to version 2.2 contains an authorization bypass vulnerability. Authenticated users with contributor-level access or higher can exploit the static_block_content shortcode to read private or draft posts by specifying arbitrary post IDs. This occurs because the plugin does not verify post status or user permissions before outputting post content.
AI Analysis
Technical Summary
CVE-2026-10780 describes an Insecure Direct Object Reference vulnerability (CWE-639) in the Static Block plugin for WordPress versions up to and including 2.2. The static_block_content() shortcode handler uses an attacker-supplied 'id' attribute to retrieve posts via get_post() without checking the post's status or the requesting user's capabilities. This allows authenticated users with contributor-level privileges or higher to access the content of private, draft, or pending posts, including administrator-created static blocks, by embedding the shortcode with arbitrary post IDs in their content and previewing it.
Potential Impact
Authenticated attackers with contributor-level access or higher can read the contents of arbitrary posts, including private and draft posts that should normally be restricted. This leads to unauthorized disclosure of potentially sensitive information contained in static blocks or other post types.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict contributor-level access or higher to trusted users only. Monitor for updates from the plugin author or WordPress security advisories regarding an official fix.
CVE-2026-10780: CWE-639 Authorization Bypass Through User-Controlled Key in mohammadtanzilurrahman Static Block
Description
The Static Block WordPress plugin up to version 2.2 contains an authorization bypass vulnerability. Authenticated users with contributor-level access or higher can exploit the static_block_content shortcode to read private or draft posts by specifying arbitrary post IDs. This occurs because the plugin does not verify post status or user permissions before outputting post content.
CVSS v3.1
Score 4.3medium
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-10780 describes an Insecure Direct Object Reference vulnerability (CWE-639) in the Static Block plugin for WordPress versions up to and including 2.2. The static_block_content() shortcode handler uses an attacker-supplied 'id' attribute to retrieve posts via get_post() without checking the post's status or the requesting user's capabilities. This allows authenticated users with contributor-level privileges or higher to access the content of private, draft, or pending posts, including administrator-created static blocks, by embedding the shortcode with arbitrary post IDs in their content and previewing it.
Potential Impact
Authenticated attackers with contributor-level access or higher can read the contents of arbitrary posts, including private and draft posts that should normally be restricted. This leads to unauthorized disclosure of potentially sensitive information contained in static blocks or other post types.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict contributor-level access or higher to trusted users only. Monitor for updates from the plugin author or WordPress security advisories regarding an official fix.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-06-03T16:01:12.626Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a30e6730b89be68884f4f56
Added to database: 06/16/2026, 06:00:19 UTC
Last enriched: 06/23/2026, 15:26:25 UTC
Last updated: 07/31/2026, 19:22:57 UTC
Views: 65
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.