On this page
CVE Details
- Protection status: Protected by Atomicorp rules · About protection statuses
- CVE: CVE-2026-3481
- Name: WP Blockade <= 0.9.14 - Reflected Cross-Site Scripting via ‘shortcode’ Parameter
- Severity: Medium
- CVSS: 6.1 (v3.1) (Medium)
- CVSS version: 3.1
- CVSS source: Wordfence CNA
- CVSS vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N- Attack vector: Network
- Attack complexity: Low
- Privileges required: None
- User interaction: Required
- Scope: Changed
- Confidentiality impact: Low
- Integrity impact: Low
- Availability impact: None
- CWE: CWE-79 — Improper Neutralization of Input During Web Page Generation
- Related CAPEC attack patterns (via MITRE CWE relationships): CAPEC-209 (opens in a new tab) , CAPEC-588 (opens in a new tab) , CAPEC-591 (opens in a new tab) , CAPEC-592 (opens in a new tab) , CAPEC-63 (opens in a new tab) , CAPEC-85 (opens in a new tab)
- Vendor: burlingtonbytes
- Vulnerable product: WP Blockade – Visual Page Builder
- CVE published: 2026-05-22
- CVE last modified: 2026-07-23
- EPSS: 0.0025; 16.5th percentile as of 2026-11-20 (FIRST (opens in a new tab) )
- Latest Update: 2026-11-10
- Selected Rule IDs observed: 333140 , 340087 , 340099 , 340147 , 341099 , 341266
- Matching rules: 6; rules with blocking actions: 6
- Would-block Rule IDs: 333140 , 340087 , 340099 , 340147 , 341099 , 341266
- Request surfaces inspected: JSON request data, Request URI, Request argument names, Request arguments, Request cookies, Request headers, SOAP request data, XML request data
Technical vulnerability details · CVSS assessments, exploit evidence & CPE data
CVSS assessments
CVSS v3.1 · security@wordfence.com
- Base score: 6.1
- Base severity: MEDIUM
- Exploitability subscore: 2.8
- Impact subscore: 2.7
- Assessment type: Secondary
- Source identifier: security@wordfence.com
- Full vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N- Attack vector: Network
- Attack complexity: Low
- Privileges required: None
- User interaction: Required
- Scope: Changed
- Confidentiality impact: Low
- Integrity impact: Low
- Availability impact: None
- Exploit maturity: Not scored
Exploitability and impact subscores describe the vulnerability’s technical characteristics. Exploit maturity describes the reported state of exploitation; these are separate measures.
Assessment source: NVD record (opens in a new tab) · CVE record (opens in a new tab)
CISA SSVC assessments
These are CISA’s published decision points at the assessment time. They are not a complete organization-specific prioritization decision.
- Provider: CISA ADP
- Provider identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
- SSVC version: 2.0.3
- Role: CISA Coordinator
- Assessment timestamp: 2026-05-22T12:35:59.570293Z
- Exploitation: none
- Automatable: no
- Technical Impact: partial
- Source: CISA ADP in the CVE record (opens in a new tab)
Vulnerable CPE configurations
No vulnerable CPE configurations are supplied in the current NVD record. See the affected-product information and vendor guidance on this page.
Vulnerability Description
The WP Blockade plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the ‘shortcode’ parameter in all versions up to and including 0.9.14. This is due to insufficient input sanitization and output escaping in the render_shortcode_preview() function. The function receives user input from $GET[‘shortcode’], passes it through stripslashes() without any sanitization, and then outputs it directly via echo do_shortcode($shortcode) on line 393. When the input is not a valid WordPress shortcode (e.g., an HTML tag with JavaScript event handlers), do_shortcode() returns it unchanged, and it is reflected into the page without escaping. The endpoint is registered via admin_post (not admin_post_nopriv_), meaning it requires the user to be logged in with at minimum a Subscriber-level account. There is no nonce verification or additional capability check. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject arbitrary web scripts in pages that will execute if they can successfully trick a user into performing an action such as clicking a link.
Recommended Actions
Maintain the observed Atomicorp protections. Keep your Atomicorp commercial rules current and confirm that the selected observed rules (333140 , 340087 , 340099 , 340147 , 341099 , 341266 ) have not been locally disabled. Atomicorp commercial rules are enabled by default. If you use Atomic WAF, review the applicable policy and rule settings.
Apply the vendor’s remediation. WAF protection is defense in depth and does not replace upgrading or following the affected vendor’s guidance.
- Affected versions: burlingtonbytes WP Blockade – Visual Page Builder versions through 0.9.14.
- No specific CNA/vendor solution or workaround is included in the current CVE Record (opens in a new tab) . Review the vendor’s security advisories and supported-release guidance before making changes.
Validate after changes. Confirm rule updates are current, review WAF events for the affected application, and test application behavior after vendor upgrades, mitigations, or local policy changes.
Research Notes
Atomicorp WAF protections are designed around attack techniques and exploit behaviors, allowing existing protections to apply across multiple vulnerabilities without requiring a unique rule for every CVE.
Public Vulnerability References
- NVD (opens in a new tab)
- CVE Record (opens in a new tab)
- CVE authority reference: https://plugins.trac.wordpress.org/browser/wp-blockade/tags/0.9.14/wp-blockade.php#L360 (opens in a new tab)
- CVE authority reference: https://plugins.trac.wordpress.org/browser/wp-blockade/tags/0.9.14/wp-blockade.php#L393 (opens in a new tab)
- CVE authority reference: https://plugins.trac.wordpress.org/browser/wp-blockade/trunk/wp-blockade.php#L360 (opens in a new tab)
- CVE authority reference: https://plugins.trac.wordpress.org/browser/wp-blockade/trunk/wp-blockade.php#L393 (opens in a new tab)
- CVE authority reference: https://www.wordfence.com/threat-intel/vulnerabilities/id/66950509-ce2a-42fe-a8b2-2a92a1b573c3?source=cve (opens in a new tab)
Test or Research Source
- Source: Atomicorp AI Research Framework
- Tags: cve, derived, waf-probe, xss
Research Note Context
This research note documents exploit-technique analysis associated with this vulnerability and references Atomicorp WAF protections observed during engineering review, testing, or validation activities.
Atomicorp security controls are generally designed to identify and mitigate attack techniques and exploit behaviors rather than individual CVE identifiers. As a result, protections developed for one vulnerability may also apply to related attack variants and future vulnerabilities using similar techniques.
Learn More
Atomicorp develops commercially supported security technologies for web applications, servers, endpoints, workloads, and legacy enterprise platforms.
Organizations interested in protecting systems against exploit techniques associated with vulnerabilities such as this one can learn more about:
- Atomic ModSecurity Rules: commercially maintained WAF rules for ModSecurity deployments, including protections for web attacks, bots, scanners, malware, exploitation attempts, and emerging vulnerability classes.
- Atomic WAF: an enterprise web application firewall with Atomicorp rules, centralized management, reporting, authentication controls, and operational tooling.
- Atomic ModSecurity Integrator: a special licensing option for MSPs, MSSPs, OEMs, VARs, reverse proxy providers, and other integrators who want to incorporate Atomicorp ModSecurity rule technology into their own products or services.
- Atomic OSSEC: an enterprise OSSEC-based intrusion detection, compliance, and security monitoring platform.
- Atomic Protector: workload protection for Linux, web, cloud, data center, and hybrid environments.
For additional information, product evaluations, or technical discussions, visit https://www.atomicorp.com/ or https://modsecurity.io/ (opens in a new tab) .