CVE-2026-12430

Blocksy Companion <= 2.1.45 - Authenticated (Editor+) Stored Cross-Site Scripting via 'product_description' Parameter

2026-06-18 15:44
Pasindu Dilshan (K4PXD)

Strategic Overview

Status
Patched in 2.1.46
Affected Plugin
Blocksy Companion
Affected Version
<= 2.1.45
CVSS
4.4Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2026-12430
View all Blocksy Companion vulnerabilities

At a glance

CVE-2026-12430 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Blocksy Companion WordPress plugin, affecting versions <= 2.1.45. It carries a CVSS score of 4.4 (reachable over the network). Exploitation requires an authenticated account at Editor level or above. The issue is fixed in version 2.1.46; sites on affected versions should update now. Disclosed June 2026, reported by Pasindu Dilshan (K4PXD).

Vulnerability Overview

The Blocksy Companion plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 2.1.45 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with editor-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user.

CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Reaching this weakness in Blocksy Companion <= 2.1.45 takes an account at Editor level or above. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.

Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Blocksy Companion the fix is 2.1.46: builds <= 2.1.45 are affected, anything from 2.1.46 onward is not.

Remediation

Update to version 2.1.46, or a newer patched version

How does WordSec protect against this?

An attacker needs Editor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Blocksy Companion 2.1.46 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-12430https://www.wordfence.com/threat-intel/vulnerabilities/id/fac4ae61-cfc6-4efc-9f57-58fa39e00f07https://nvd.nist.gov/vuln/detail/CVE-2026-12430

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C