CVE-2021-4411

WP EasyPay – Square for WordPress <= 3.2.0 - Cross-Site Request Forgery Bypass

2021-07-05 00:00
Jerome Bruandet

Strategic Overview

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

At a glance

CVE-2021-4411 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP Easy Pay WordPress plugin, affecting versions <= 3.2.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 3.2.3; sites on affected versions should update now. Disclosed July 2021, reported by Jerome Bruandet.

Vulnerability Overview

The WP EasyPay – Square for WordPress plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.2.0. This is due to missing or incorrect nonce validation on the wpep_download_transaction_in_excel() function. This makes it possible for unauthenticated attackers to trigger a transactions download 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)

WP Easy Pay <= 3.2.0 carries this weakness at wpep_download_transaction_in_excel(), and reaching it 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 3.2.3: builds <= 3.2.0 are affected, anything from 3.2.3 onward is not.

Remediation

Update to version 3.2.3, 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 3.2.3 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2021-4411https://www.wordfence.com/threat-intel/vulnerabilities/id/a1fbb3a6-fcc2-47c5-a086-331e69292addhttps://nvd.nist.gov/vuln/detail/CVE-2021-4411

Related records

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