# CVE-2026-3480: Missing authorization in WP Blockade – Visual Page Builder

> Authenticated users can execute arbitrary shortcodes due to missing authorization checks, potentially leading to code execution or privilege escalation.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Apr 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-3q32-77vq-vq6v

## What is CVE-2026-3480?

CVE-2026-3480 is a medium-severity missing authorization vulnerability in burlingtonbytes WP Blockade – Visual Page Builder, published on 8 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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).

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-3480?


## How do I fix CVE-2026-3480?

No fix has been published for CVE-2026-3480 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-3480 being exploited?

There is no known exploitation of CVE-2026-3480 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-3480 and fix it if it is affected.

What it is: CVE-2026-3480 is a medium-severity missing authorization vulnerability in burlingtonbytes WP Blockade – Visual Page Builder, published on 8 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-3480 in the wild and no public exploit code.

Affected product: burlingtonbytes WP Blockade – Visual Page Builder. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-3480/ (Markdown: https://insights.sbomify.com/CVE-2026-3480/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-3480
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-3480
- OSV: https://osv.dev/vulnerability/CVE-2026-3480

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-3480/
Summaries are generated and may contain mistakes; the official description above is the record.