dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-3480

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The WP Blockade plugin for WordPress is vulnerable to Missing Authorization in all versions up to and including 0.9.14. The plugin registers an admin_post action hook 'wp-blockade-shortcode-render' that maps to the render_shortcode_preview() function. This function lacks any capability check (current_user_can()) and nonce verification, allowing any authenticated user to execute arbitrary WordPress shortcodes. The function takes a user-supplied 'shortcode' parameter from $_GET, passes it through stripslashes(), and directly executes it via do_shortcode(). This makes it possible for authenticated attackers, with Subscriber-level access and above, to execute arbitrary shortcodes, which could lead to information disclosure, privilege escalation, or other impacts depending on what shortcodes are registered on the site (e.g., shortcodes from other plugins that display sensitive data, perform actions, or include files).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The WP Blockade plugin for WordPress lacks authorization checks on its render_shortcode_preview() function, which is registered via the admin_post hook 'wp-blockade-shortcode-render'. Any authenticated user with Subscriber-level access or higher can supply an arbitrary shortcode via the $_GET['shortcode'] parameter, which gets processed through stripslashes() and executed via do_shortcode() without any capability verification or nonce validation.

MitigationAdd a capability check (e.g., current_user_can('edit_posts')) and nonce verification to the render_shortcode_preview() function to ensure only authorized users can render shortcodes.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify WP Blockade plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate WP Blockade. Note the installed version number.
    Affected if WP Blockade plugin is active and installed without a version that includes the security fix
  2. Confirm the vulnerable hook exists in plugin code
    Access the plugin files via FTP or file manager, locate the file containing render_shortcode_preview() function, and verify it is hooked to 'wp-blockade-shortcode-render' and triggered via admin_post action.
    Affected if The render_shortcode_preview() function is hooked to admin_post without capability checks or nonce verification
  3. Check for the vulnerable shortcode parameter handling
    In the plugin code, examine the render_shortcode_preview() function to confirm it directly uses $_GET['shortcode'] passed to stripslashes() and then do_shortcode() without sanitization or authorization.
    Affected if The function directly executes do_shortcode() on user-supplied $_GET['shortcode'] without current_user_can() check or nonce verification
  4. Identify users with Subscriber-level access
    In WordPress admin, go to Users > All Users and check if any users exist with the Subscriber role.
    Affected if There are users with Subscriber-level access or higher who could exploit this vulnerability via the admin_post endpoint
  5. Test endpoint accessibility
    Send a GET request to your site admin-post.php?action=wp-blockade-shortcode-render&shortcode=[any_shortcode] while authenticated as a Subscriber-level user to verify the shortcode executes.
    Affected if The endpoint executes shortcodes for authenticated users with Subscriber-level access without authorization checks

Your environment is affected if the WP Blockade plugin is installed, the render_shortcode_preview() function lacks authorization checks, and any Subscriber-level user account exists on the site.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Add a capability check (e.g., current_user_can('edit_posts')) and nonce verification to the render_shortcode_preview() function to ensure only authorized users can render shortcodes.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3480 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3480 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data