CVE-2024-10671

Button Block – Get fully customizable & multi-functional buttons <= 1.1.4 - Authenticated (Contributor+) Post Disclosure

2024-11-20 00:00
Francesco Carlucci

Strategic Overview

Status
Patched in 1.1.5
Affected Plugin
Button Block – Stylish buttons that get more clicks
Affected Version
<= 1.1.4
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2024-10671
View all Button Block – Stylish buttons that get more clicks vulnerabilities

At a glance

CVE-2024-10671 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Button Block WordPress plugin, affecting versions <= 1.1.4. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 1.1.5; sites on affected versions should update now. Disclosed November 2024, reported by Francesco Carlucci.

Vulnerability Overview

The Button Block – Get fully customizable & multi-functional buttons plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 1.1.4 via the [btn_block] shortcode due to insufficient restrictions on which posts can be included. This makes it possible for authenticated attackers, with Contributor-level access and above, to extract data from password protected, private, or draft posts that they should not have access to.

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 Button Block <= 1.1.4 takes an account at Contributor 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 Button Block the fix is 1.1.5: builds <= 1.1.4 are affected, anything from 1.1.5 onward is not.

Remediation

Update to version 1.1.5, 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: Button Block 1.1.5 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-10671https://www.wordfence.com/threat-intel/vulnerabilities/id/99c7eead-2cf2-4663-9328-671274f3c436https://nvd.nist.gov/vuln/detail/CVE-2024-10671

Related records

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