CVE-2023-2078

Buy Me a Coffee – Button and Widget Plugin <= 3.7 - Missing Authorization

2023-07-10 00:00
István Márton

Strategic Overview

Status
Patched in 3.8
Affected Version
<= 3.7
CVSS
7.3High
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2023-2078
View all Buy Me a Coffee – Button and Widget Plugin vulnerabilities

At a glance

CVE-2023-2078 is a high-severity Missing Authorization vulnerability in the Buy Me a Coffee WordPress plugin, affecting versions <= 3.7. It carries a CVSS score of 7.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.8; sites on affected versions should update now. Disclosed July 2023, reported by István Márton.

Vulnerability Overview

The "Buy Me a Coffee – Button and Widget Plugin" plugin for WordPress is vulnerable to unauthorized modification of data due to missing capability checks on the recieve_post, bmc_disconnect, name_post, and widget_post functions in versions up to, and including, 3.7. This makes it possible for authenticated attackers, with minimal permissions such as subscribers, to update the plugins settings. CVE-2023-25030 may be a duplicate of this issue.

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

Reaching this weakness in Buy Me a Coffee <= 3.7 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 Buy Me a Coffee the fix is 3.8: builds <= 3.7 are affected, anything from 3.8 onward is not.

Remediation

Update to version 3.8, 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: Buy Me a Coffee 3.8 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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