CVE-2024-5861: CWE-862 Missing Authorization in wpexpertsio WP EasyPay – Square for WordPress
CVE-2024-5861 is a medium-severity vulnerability in the WP EasyPay – Square for WordPress plugin that allows unauthenticated attackers to disconnect the Square payment integration due to a missing authorization check in the wpep_square_disconnect() function. This flaw affects all plugin versions up to 4. 2. 3 and does not require user interaction or privileges to exploit. While it does not impact confidentiality or availability, it allows unauthorized modification of payment configuration, potentially disrupting payment processing. No known exploits are currently reported in the wild. Organizations using this plugin should prioritize patching or applying mitigations to prevent unauthorized disconnection of Square payment services, which could lead to business disruption and loss of customer trust. Countries with significant WordPress usage and e-commerce reliance are most at risk.
AI Analysis
Technical Summary
The vulnerability identified as CVE-2024-5861 affects the WP EasyPay – Square for WordPress plugin, a widely used integration that enables WordPress sites to accept payments via Square. The root cause is a missing authorization check (CWE-862) in the wpep_square_disconnect() function, which handles the disconnection of the Square payment gateway. Because this function lacks a capability check, unauthenticated attackers can invoke it remotely, disconnecting the Square payment integration without any credentials or user interaction. This vulnerability impacts all versions of the plugin up to and including 4.2.3. The CVSS 3.1 base score is 5.3 (medium), reflecting that the attack vector is network-based (AV:N), requires no privileges (PR:N), and no user interaction (UI:N). The impact is limited to integrity, as attackers can modify the payment configuration by disconnecting Square, but confidentiality and availability remain unaffected. No patches or exploit code are currently publicly available, and no known active exploitation has been reported. However, the ability to disrupt payment processing can have significant operational and reputational consequences for affected websites. The vulnerability was publicly disclosed on July 24, 2024, and assigned by Wordfence.
Potential Impact
The primary impact of CVE-2024-5861 is the unauthorized modification of payment gateway configuration, specifically the disconnection of the Square payment service on affected WordPress sites. This can lead to disruption of payment processing, resulting in lost sales and customer dissatisfaction. Although the vulnerability does not expose sensitive data or cause denial of service, the integrity compromise can undermine trust in the affected e-commerce platforms. Attackers could exploit this flaw to cause intermittent or prolonged payment outages, potentially impacting revenue streams. Organizations relying on WP EasyPay – Square for WordPress for their payment processing are at risk of operational disruption. The ease of exploitation (no authentication or user interaction required) increases the likelihood of opportunistic attacks, especially on high-traffic commercial websites. While no known exploits are currently in the wild, the vulnerability’s public disclosure may prompt attackers to develop exploit tools.
Mitigation Recommendations
To mitigate CVE-2024-5861, organizations should immediately update the WP EasyPay – Square for WordPress plugin to a version that includes the missing authorization check once released by the vendor. Until a patch is available, administrators can implement the following practical measures: 1) Restrict access to the WordPress REST API endpoints or AJAX handlers associated with the wpep_square_disconnect() function using web application firewall (WAF) rules or server-level access controls to block unauthenticated requests. 2) Monitor logs for suspicious requests targeting the disconnect function and alert on anomalies. 3) Employ WordPress security plugins that can enforce capability checks or limit access to sensitive plugin functions. 4) Regularly audit and review payment gateway configurations to detect unauthorized changes promptly. 5) Educate site administrators about the vulnerability and the importance of timely updates. These steps help reduce the attack surface and detect exploitation attempts before the official patch is applied.
Affected Countries
United States, Canada, United Kingdom, Australia, Germany, France, India, Brazil, Japan, Netherlands, Italy, Spain
CVE-2024-5861: CWE-862 Missing Authorization in wpexpertsio WP EasyPay – Square for WordPress
Description
CVE-2024-5861 is a medium-severity vulnerability in the WP EasyPay – Square for WordPress plugin that allows unauthenticated attackers to disconnect the Square payment integration due to a missing authorization check in the wpep_square_disconnect() function. This flaw affects all plugin versions up to 4. 2. 3 and does not require user interaction or privileges to exploit. While it does not impact confidentiality or availability, it allows unauthorized modification of payment configuration, potentially disrupting payment processing. No known exploits are currently reported in the wild. Organizations using this plugin should prioritize patching or applying mitigations to prevent unauthorized disconnection of Square payment services, which could lead to business disruption and loss of customer trust. Countries with significant WordPress usage and e-commerce reliance are most at risk.
AI-Powered Analysis
Technical Analysis
The vulnerability identified as CVE-2024-5861 affects the WP EasyPay – Square for WordPress plugin, a widely used integration that enables WordPress sites to accept payments via Square. The root cause is a missing authorization check (CWE-862) in the wpep_square_disconnect() function, which handles the disconnection of the Square payment gateway. Because this function lacks a capability check, unauthenticated attackers can invoke it remotely, disconnecting the Square payment integration without any credentials or user interaction. This vulnerability impacts all versions of the plugin up to and including 4.2.3. The CVSS 3.1 base score is 5.3 (medium), reflecting that the attack vector is network-based (AV:N), requires no privileges (PR:N), and no user interaction (UI:N). The impact is limited to integrity, as attackers can modify the payment configuration by disconnecting Square, but confidentiality and availability remain unaffected. No patches or exploit code are currently publicly available, and no known active exploitation has been reported. However, the ability to disrupt payment processing can have significant operational and reputational consequences for affected websites. The vulnerability was publicly disclosed on July 24, 2024, and assigned by Wordfence.
Potential Impact
The primary impact of CVE-2024-5861 is the unauthorized modification of payment gateway configuration, specifically the disconnection of the Square payment service on affected WordPress sites. This can lead to disruption of payment processing, resulting in lost sales and customer dissatisfaction. Although the vulnerability does not expose sensitive data or cause denial of service, the integrity compromise can undermine trust in the affected e-commerce platforms. Attackers could exploit this flaw to cause intermittent or prolonged payment outages, potentially impacting revenue streams. Organizations relying on WP EasyPay – Square for WordPress for their payment processing are at risk of operational disruption. The ease of exploitation (no authentication or user interaction required) increases the likelihood of opportunistic attacks, especially on high-traffic commercial websites. While no known exploits are currently in the wild, the vulnerability’s public disclosure may prompt attackers to develop exploit tools.
Mitigation Recommendations
To mitigate CVE-2024-5861, organizations should immediately update the WP EasyPay – Square for WordPress plugin to a version that includes the missing authorization check once released by the vendor. Until a patch is available, administrators can implement the following practical measures: 1) Restrict access to the WordPress REST API endpoints or AJAX handlers associated with the wpep_square_disconnect() function using web application firewall (WAF) rules or server-level access controls to block unauthenticated requests. 2) Monitor logs for suspicious requests targeting the disconnect function and alert on anomalies. 3) Employ WordPress security plugins that can enforce capability checks or limit access to sensitive plugin functions. 4) Regularly audit and review payment gateway configurations to detect unauthorized changes promptly. 5) Educate site administrators about the vulnerability and the importance of timely updates. These steps help reduce the attack surface and detect exploitation attempts before the official patch is applied.
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Wordfence
- Date Reserved
- 2024-06-11T13:40:46.469Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 699f6bf3b7ef31ef0b55cfc9
Added to database: 2/25/2026, 9:38:59 PM
Last enriched: 2/26/2026, 2:53:27 AM
Last updated: 2/26/2026, 9:39:40 AM
Views: 1
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-28138: Deserialization of Untrusted Data in Stylemix uListing
HighCVE-2026-28136: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in VeronaLabs WP SMS
HighCVE-2026-28132: Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) in villatheme WooCommerce Photo Reviews
HighCVE-2026-28131: Insertion of Sensitive Information Into Sent Data in WPVibes Elementor Addon Elements
HighCVE-2026-28083: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in UX-themes Flatsome
HighActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.