{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-3481 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-3481 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-3481 is a medium-severity cross-site scripting vulnerability in burlingtonbytes WP Blockade – Visual Page Builder, published on 22 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-3481 and fix it if it is affected.\n\nWhat it is: CVE-2026-3481 is a medium-severity cross-site scripting vulnerability in burlingtonbytes WP Blockade – Visual Page Builder, published on 22 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-3481 in the wild and no public exploit code.\n\nAffected product: burlingtonbytes WP Blockade – Visual Page Builder. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-3481/ (Markdown: https://insights.sbomify.com/CVE-2026-3481/index.md)","id":"CVE-2026-3481","markdown":"https://insights.sbomify.com/CVE-2026-3481/index.md","name":"CVE-2026-3481","record":{"aliases":["GHSA-p9mp-xq3w-289v"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Authenticated attackers can inject arbitrary scripts via the shortcode parameter, potentially leading to session hijacking or malicious actions on behalf of other users.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":6.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"WP Blockade \u003c= 0.9.14 - Reflected Cross-Site Scripting via 'shortcode' Parameter","id":"CVE-2026-3481","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"IBM Sterling B2B Integrator and IBM Sterling File Gateway Authorization Bypass","id":"CVE-2026-3482"},"packages":[],"prev":{"headline":"Missing authorization in WP Blockade – Visual Page Builder","id":"CVE-2026-3480"},"products":["WP Blockade – Visual Page Builder"],"published":"2026-05-22","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-22","vendors":["burlingtonbytes"]},"summary":"Authenticated attackers can inject arbitrary scripts via the shortcode parameter, potentially leading to session hijacking or malicious actions on behalf of other users.","url":"https://insights.sbomify.com/CVE-2026-3481/"}