CVE-2023-41693

MyCryptoCheckout <= 2.125 - Cross-Site Request Forgery

2023-09-04 00:00
qilin_99

Strategic Overview

Status
Patched in 2.126
Affected Version
<= 2.125
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-41693
View all MyCryptoCheckout – Bitcoin, Ethereum, and 100+ altcoins for WooCommerce vulnerabilities

At a glance

CVE-2023-41693 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the MyCryptoCheckout WordPress plugin, affecting versions <= 2.125. 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 2.126; sites on affected versions should update now. Disclosed September 2023, reported by qilin_99.

Vulnerability Overview

The MyCryptoCheckout plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.125. This is due to missing nonce validation in the ~/vendor/plainview/sdk/wordpress/form2/form.php file. This makes it possible for unauthenticated attackers to perform unauthorized actions 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 MyCryptoCheckout <= 2.125 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 MyCryptoCheckout the fix is 2.126: builds <= 2.125 are affected, anything from 2.126 onward is not.

Remediation

Update to version 2.126, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

Related records

Other vulnerabilities in MyCryptoCheckout – Bitcoin, Ethereum, and 100+ altcoins for WooCommerce

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