CVE-2022-4004

Donation Button <= 4.0.0 - Missing Authorization

2022-11-16 00:00
István Márton

Strategic Overview

Status
Unpatched
Affected Plugin
Donation Button
Affected Version
<= 4.0.0
CVSS
5.4Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2022-4004
View all Donation Button vulnerabilities

At a glance

CVE-2022-4004 is a medium-severity Missing Authorization vulnerability in the Donation Button WordPress plugin, affecting versions <= 4.0.0. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed November 2022, reported by István Márton.

Vulnerability Overview

The Donation Button plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on the donation_button_twilio_send_test_sms AJAX action in versions up to, and including, 4.0.0. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to use the plugin's Twilio integration to send SMS messages to arbitrary phone numbers.

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-862: Missing Authorization

Reaching this weakness in Donation Button <= 4.0.0 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. No fixed build of this plugin is recorded for Donation Button yet, so installs running <= 4.0.0 stay exposed until the vendor ships one.

Remediation

No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.

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. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.

  • Login Security
  • Alerts

External References

Related records

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