CVE-2023-49154

Button Generator – easily Button Builder <= 2.3.8 - Missing Authorization

2023-11-28 00:00
Elliot

Strategic Overview

Status
Patched in 2.3.9
Affected Plugin
Button Generator – Easily Create Custom Buttons with Icons and Analytics
Affected Version
<= 2.3.8
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2023-49154
View all Button Generator – Easily Create Custom Buttons with Icons and Analytics vulnerabilities

At a glance

CVE-2023-49154 is a medium-severity Missing Authorization vulnerability in the Button Generator WordPress plugin, affecting versions <= 2.3.8. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.3.9; sites on affected versions should update now. Disclosed November 2023, reported by Elliot.

Vulnerability Overview

The Button Generator – easily Button Builder plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the function btg_count() function in versions up to, and including, 2.3.8. This makes it possible for unauthenticated attackers to reset the button counter.

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 privileges on the target site, and no interaction from a victim user.

CWE-862: Missing Authorization

Button Generator <= 2.3.8 carries this weakness at btg_count(), and reaching it takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Button Generator the fix is 2.3.9: builds <= 2.3.8 are affected, anything from 2.3.9 onward is not.

Remediation

Update to version 2.3.9, 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 Generator 2.3.9 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-49154https://www.wordfence.com/threat-intel/vulnerabilities/id/73dd286e-5338-42d2-9928-1e14150ccf56https://nvd.nist.gov/vuln/detail/CVE-2023-49154

Related records

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