CVE-2023-25443

Button Generator – easily Button Builder <= 2.3.5 - Cross-Site Request Forgery in tools-data-base.php

2023-05-25 00:00
Rio Darmawan

Strategic Overview

Status
Patched in 2.3.6
Affected Version
<= 2.3.5
CVSS
5.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-25443
View all Button Generator – Easily Create Custom Buttons with Icons and Analytics vulnerabilities

At a glance

CVE-2023-25443 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Button Generator WordPress plugin, affecting versions <= 2.3.5. 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.6; sites on affected versions should update now. Disclosed May 2023, reported by Rio Darmawan.

Vulnerability Overview

The Button Generator – easily Button Builder plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.3.5. This is due to missing or incorrect nonce validation in the tools-data-base.php file. This makes it possible for unauthenticated attackers to delete buttons via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in Button Generator <= 2.3.5 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Button Generator the fix is 2.3.6: builds <= 2.3.5 are affected, anything from 2.3.6 onward is not.

Remediation

Update to version 2.3.6, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Button Generator: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Button Generator 2.3.6 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

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