CVE-2024-12560

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

2024-12-18 00:00
Webbernaut

Strategic Overview

Status
Patched in 1.1.6
Affected Version
<= 1.1.5
CVSS
4.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2024-12560
View all Button Block – Stylish buttons that get more clicks vulnerabilities

At a glance

CVE-2024-12560 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Button Block WordPress plugin, affecting versions <= 1.1.5. 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.6; sites on affected versions should update now. Disclosed December 2024, reported by Webbernaut.

Vulnerability Overview

The Button Block – Get fully customizable & multi-functional buttons plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.1.5 via the 'btn_block_duplicate_post' function. This makes it possible for authenticated attackers, with Contributor-level access and above, to extract potentially sensitive data from draft, scheduled (future), private, and password protected 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-200: Exposure of Sensitive Information to an Unauthorized Actor

Button Block <= 1.1.5 carries this weakness at btn_block_duplicate_post, and reaching it takes an account at Contributor level or above. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Button Block the fix is 1.1.6: builds <= 1.1.5 are affected, anything from 1.1.6 onward is not.

Remediation

Update to version 1.1.6, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: Button Block 1.1.6 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

Related records

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