Is MyCryptoCheckout safe to use?

Laskyr does not give safety verdicts. No known unpatched vulnerabilities in the latest version (2.172). As of 2026-11-04. 3 issues are on record for older versions; version 2.162 or newer fixes all of them that state a fix. Keep MyCryptoCheckout on the latest version (2.172) and remove it if you do not use it.

Which versions of MyCryptoCheckout are vulnerable?

Known issues on record (newest first): Missing authorization check (2.161 and older, fixed in 2.162); Cross-site request forgery (CSRF) (2.125 and older, fixed in 2.126); Reflected cross-site scripting (XSS) (older than 2.124, fixed in 2.124). The full list with sources is on this page.

What is the latest version of MyCryptoCheckout?

2.172, according to wordpress.org (last updated 2026-08-19). It has 8,000+ active installs.

What should I do if my MyCryptoCheckout is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update mycryptocheckout). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · mycryptocheckout · data as of 2026-11-04

Is MyCryptoCheckout safe? Known vulnerabilities and latest version

Latest version: 2.172
Last updated: 2026-08-19
Active installs: 8,000+
Known issues on record: 3
Unpatched in latest: 0
Tested up to WP: 7.1.4 · PHP 8.0+

Crypto payment gateway for WooCommerce and Easy Digital Downloads. Accept 100+ coins: Bitcoin, Ethereum, BNB, Solana. Peer2Peer transactions. — by edward_plainview

What to do

Update to the latest version (2.172). Anything older than 2.162 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
If you cannot update right away, deactivate it until you can.
Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get mycryptocheckout --field=version shows what you run; wp plugin update mycryptocheckout updates it.

Check your version

Known vulnerabilities

3 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

high 7.5 CVE-2026-45209 · published 2026-05-25

Missing authorization check in MyCryptoCheckout (2.161 and older)

Affected: 2.161 and older
Fixed in: 2.162
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Missing Authorization vulnerability in edward_plainview MyCryptoCheckout allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects MyCryptoCheckout: from n/a through 2.161.

NVD CVE-2026-45209 Patchstack advisory

high 8.8 CVE-2023-41693 · published 2023-10-03

Cross-site request forgery (CSRF) in MyCryptoCheckout (2.125 and older)

Affected: 2.125 and older
Fixed in: 2.126
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

Cross-Site Request Forgery (CSRF) vulnerability in edward_plainview MyCryptoCheckout plugin <= 2.125 versions.

NVD CVE-2023-41693 Patchstack advisory

medium 6.1 CVE-2023-1546 · published 2023-05-02

Reflected cross-site scripting (XSS) in MyCryptoCheckout (older than 2.124)

Affected: older than 2.124
Fixed in: 2.124
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

The MyCryptoCheckout WordPress plugin before 2.124 does not escape some URLs before outputting them in attributes, leading to Reflected Cross-Site Scripting

NVD CVE-2023-1546 WPScan advisory

Recent activity

2026-08-19 — latest release on wordpress.org (2.172).
2026-05-25 — Missing authorization check disclosed (CVE-2026-45209), fixed in 2.162.
2023-10-03 — Cross-site request forgery (CSRF) disclosed (CVE-2023-41693), fixed in 2.126.
2023-05-02 — Reflected cross-site scripting (XSS) disclosed (CVE-2023-1546), fixed in 2.124.

Free. We check the CVE feeds every day and email you only when a new issue for MyCryptoCheckout (mycryptocheckout) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Missing authorization (1) · Cross-site request forgery (CSRF) (1) · Cross-site scripting (XSS) (1)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/mycryptocheckout (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/mycryptocheckout"><img src="https://laskyr.com/plugins/mycryptocheckout/badge.svg" alt="MyCryptoCheckout vulnerability status"></a>

← Check another plugin · Free hacked-site scan

Is MyCryptoCheckout safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (2.172)

What to do

Check your version

Known vulnerabilities

Missing authorization check in MyCryptoCheckout (2.161 and older)

Cross-site request forgery (CSRF) in MyCryptoCheckout (2.125 and older)

Reflected cross-site scripting (XSS) in MyCryptoCheckout (older than 2.124)

Recent activity

Get an email when MyCryptoCheckout has a new vulnerability

Browse vulnerabilities

Where this data comes from