CVE-2023-1911

Blocksy Companion <= 1.8.81 - Authenticated(Subscriber+) Sensitive Information Exposure via blocksy_posts shortcode

2023-04-10 00:00
Erwan LR

Strategic Overview

Status
Patched in 1.8.82
Affected Plugin
Blocksy Companion
Affected Version
<= 1.8.81
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2023-1911
View all Blocksy Companion vulnerabilities

At a glance

CVE-2023-1911 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Blocksy Companion WordPress plugin, affecting versions <= 1.8.81. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.8.82; sites on affected versions should update now. Disclosed April 2023, reported by Erwan LR.

Vulnerability Overview

The Blocksy Companion plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 1.8.81 via the blocksy_posts shortcode. This can allow authenticated attackers with subscriber-level permissions or above to extract sensitive data including draft posts.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in Blocksy Companion <= 1.8.81 takes an account at Subscriber level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Blocksy Companion the fix is 1.8.82: builds <= 1.8.81 are affected, anything from 1.8.82 onward is not.

Remediation

Update to version 1.8.82, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Blocksy Companion 1.8.82 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-1911https://www.wordfence.com/threat-intel/vulnerabilities/id/d31aad1c-89d4-4f71-bfed-a795f7a4f209https://nvd.nist.gov/vuln/detail/CVE-2023-1911

Related records

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