CVE-2026-56024

WP Easy Pay – Payment and Donation form Builder for Square <= 4.5.0 - Cross-Site Request Forgery

2026-06-18 00:00
Sajjad Haqi

Strategic Overview

Status
Patched in 4.5.1
Affected Plugin
WP Easy Pay – Payment and Donation Form Builder for Square
Affected Version
<= 4.5.0
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2026-56024
View all WP Easy Pay – Payment and Donation Form Builder for Square vulnerabilities

At a glance

CVE-2026-56024 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP Easy Pay WordPress plugin, affecting versions <= 4.5.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.5.1; sites on affected versions should update now. Disclosed June 2026, reported by Sajjad Haqi.

Vulnerability Overview

The WP Easy Pay – Payment and Donation form Builder for Square plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 4.5.0. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to perform an unauthorized action 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.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in WP Easy Pay <= 4.5.0 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 WP Easy Pay the fix is 4.5.1: builds <= 4.5.0 are affected, anything from 4.5.1 onward is not.

Remediation

Update to version 4.5.1, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-56024https://www.wordfence.com/threat-intel/vulnerabilities/id/2283210d-d3b6-433f-ab17-5b29d7752aa6https://nvd.nist.gov/vuln/detail/CVE-2026-56024

Related records

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