WP Easy Pay (Free) <= 4.2.3 - Missing Authorization to Unauthenticated Service Disconnection
Strategic Overview
- Status
- Patched in 4.2.4
- Affected Plugin
- WP Easy Pay – Payment and Donation Form Builder for Square
- Affected Version
<= 4.2.3- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-5861
At a glance
CVE-2024-5861 is a medium-severity Missing Authorization vulnerability in the WP Easy Pay WordPress plugin, affecting versions <= 4.2.3. 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 4.2.4; sites on affected versions should update now. Disclosed July 2024, reported by Lucio Sá.
Vulnerability Overview
The WP EasyPay – Square for WordPress plugin for WordPress is vulnerable to unauthorized modification of datadue to a missing capability check on the wpep_square_disconnect() function in all versions up to, and including, 4.2.3. This makes it possible for unauthenticated attackers to disconnect square.
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
WP Easy Pay <= 4.2.3 carries this weakness at wpep_square_disconnect(), and reaching it takes no account at all. 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 WP Easy Pay the fix is 4.2.4: builds <= 4.2.3 are affected, anything from 4.2.4 onward is not.
Remediation
Update to version 4.2.4, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: WP Easy Pay 4.2.4 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
- 6.3CVE-2022-4974: Freemius SDK <= 2.4.2 Missing Authorization Checks
CVE-2022-4974 - 4.3CVE-2026-57808: WP Easy Pay Arbitrary Content Deletion
CVE-2026-57808 - 4.3CVE-2026-12738: WP Easy Pay Authenticated (Subscriber+) Arbitrary
CVE-2026-12738 - 4.3CVE-2026-32587: WP Easy Pay Missing Authorization
CVE-2026-32587
Other vulnerabilities in WP Easy Pay – Payment and Donation Form Builder for Square
- 6.1CVE-2023-33999: Freemius SDK <= 2.5.9 Reflected Cross-Site Scripting
CVE-2023-33999 - 6.1CVE-2023-1465: WP EasyPay <= 4.0.4 Reflected Cross-Site Scripting
CVE-2023-1465 - 5.3CVE-2026-84762: WP Easy Pay Payment Bypass
CVE-2026-84762 - 5.3CVE-2026-45215: EasyPay <= 4.3.0 Information Exposure
CVE-2026-45215 - 4.3CVE-2026-56024: WP Easy Pay CSRF
CVE-2026-56024 - 4.3CVE-2022-47177: WP EasyPay <= 4.0.4 Cross-Site Request Forgery
CVE-2022-47177 - 4.3CVE-2021-4411: WP EasyPay – Square for WordPress <= 3.2.0 CSRF Bypass
CVE-2021-4411
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C