On this page (6 sections)

A critical flaw in the CryptoPayment Gateway WordPress plugin, tracked as CVE-2026-81648, lets unauthenticated visitors run administrative operations on an affected site. According to The Hacker News, the security firm Defused Cyber has observed exploitation attempts in the wild, and no fix is known.

If you run a WordPress site that accepts cryptocurrency payments, check now whether this plugin is installed. Because the plugin appears to have no patched release, the realistic remedy is removal, followed by rotating any wallet credentials it stored.

What happened

The GitHub advisory was published on September 13, 2026 and describes a missing authorization check on one of the plugin's AJAX endpoints. Per the CVE description, that gap allows unauthenticated users to delete arbitrary files on the server, overwrite the payment gateway configuration and recover stored wallet credentials in cleartext.

On November 3, 2026, The Hacker News reported that Defused Cyber had recorded in-the-wild exploitation attempts. Defused Cyber said the attacks came from infrastructure that markets itself as "Anonymous KYC-Free VPS Hosting." This is a single reported observation from one researcher, and the research available to us does not describe how many sites were targeted or whether any attack succeeded.

Plugin status

The same report says the plugin was closed on the WordPress Plugin Directory as of August 28, 2026 and is no longer downloadable, citing an unspecified "security issue." It lists 1,845 total downloads, including 20 in the last seven days, and notes it is unclear how many sites actively run it. The affected range, 1.2.1 through 1.2.2, includes the latest version.

Why this class of bug is so dangerous

Missing authorization (CWE-862) means the code performs a sensitive action without asking who is calling it. WordPress plugins often expose functionality through AJAX endpoints, and each one needs its own permission check. When that check is absent, anyone who can reach the site over the internet can call the endpoint directly, with no login and no user interaction.

The CVSS vector in the advisory (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H) reflects this: network reachable, low complexity, no privileges, and high impact on confidentiality, integrity and availability, with a changed scope. For a payment plugin the practical consequences are serious:

  • Deleted files can take a site offline or remove security-relevant files.
  • An overwritten gateway configuration could, in principle, change where payments are directed. The research does not confirm this has happened in any real attack.
  • Wallet credentials stored in cleartext can be read, so anyone who obtains them may be able to move funds.

The advisory lists an EPSS score of 0.502% (43rd percentile), a statistical estimate of exploitation probability. It sits alongside the reported real-world attempts and does not override them.

Who is affected and how to check

You are exposed if the CryptoPayment Gateway plugin is installed, active or not, in version 1.2.1 or 1.2.2. Since the plugin is no longer in the directory, any copy on your site was installed earlier or from elsewhere. Agencies should check every client site, including staging copies reachable from the internet.

This WP-CLI command lists installed plugins with their status and version. Run it from the WordPress root on each server and look for anything named like cryptopayment or crypto payment gateway:

List installed plugins and versions (run in the WordPress root)WP-CLI
wp plugin list --fields=name,status,version

You can also look in the plugins directory over SSH. This read-only command lists plugin folders whose names contain "crypto" (the folder name may differ from the plugin's display name, so also review the full list):

List plugin folders with crypto in the name (run from the WordPress root)Shell
ls wp-content/plugins | grep -i crypto

What to do now

Caution. Deleting a payment plugin stops crypto checkout on your site. Plan a replacement payment method or a short maintenance notice first, and take a full backup before you change anything so you can investigate afterwards.
  1. Take a full backup of files and database, and keep a copy offline for later investigation.
  2. Deactivate and delete the CryptoPayment Gateway plugin on every site where it appears. Deactivating alone is not enough if the files remain reachable.
  3. Rotate every wallet key, API key and credential the plugin handled, and move funds to new wallets if you suspect exposure. Do this from a clean device.
  4. Review the payment gateway settings of any replacement plugin or your payment provider for unexpected changes, such as altered receiving addresses.
  5. Check for missing files, unexpected new files and modified core or plugin files, for example by reinstalling WordPress core and comparing against known-good copies.
  6. Review WordPress admin accounts and remove any you do not recognize, then reset passwords for administrators.
  7. Look through web server access logs for requests to admin-ajax.php from unfamiliar addresses around and after September 13, 2026.
  8. If you find signs of compromise, follow a full incident process rather than a quick cleanup.

This command searches an access log for requests to the WordPress AJAX endpoint and prints matching lines. Adjust the log path for your server; a large number of POSTs from one unfamiliar address is worth a closer look, though legitimate plugins also use this endpoint:

Search a web server access log for admin-ajax.php requests (path varies by server)Shell
grep "admin-ajax.php" /var/log/nginx/access.log | tail -n 200
Tip. Because the plugin stored credentials in cleartext, treat rotation as mandatory even if your logs look clean. Absence of evidence in logs does not prove the credentials were not read.

Detection and monitoring afterwards

Once the plugin is gone, keep watching for follow-on problems. Unexpected file deletions, changed payment settings and new admin users are the main signs to monitor. A web application firewall can add a layer in front of vulnerable endpoints; see What is a WAF? for what it can and cannot do, and note it is not a substitute for removing a plugin that has no fix.

For stores, our guide to security for online stores covers wider hardening, and Known vulnerabilities per WordPress plugin lets you look up other plugins you rely on. For general habits, see the WordPress security checklist. Webforta Monitor can also alert you to certificate, DNS and header changes on your domain via monitoring, which helps catch tampering that happens alongside an incident like this.

Timeline

Reported events for CVE-2026-81648
DateEvent
August 28, 2026Plugin closed on the WordPress Plugin Directory for an unspecified security issue (per The Hacker News)
September 13, 2026CVE published by NVD and advisory published in the GitHub Advisory Database
September 14, 2026GitHub advisory last updated
November 3, 2026The Hacker News reports exploitation attempts observed by Defused Cyber
Open questions remain: the research does not name the plugin's developer, say whether a fix is planned, or state how many live sites run the plugin. Re-check the WPScan entry for updates.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-81648 - GitHub Advisory Databasegithub.com
  2. Attackers Target Unpatched CryptoPayment Gateway Flaw That Can Expose Wallet Credentialsthehackernews.com ·
  • WordPress
  • CVE-2026-81648
  • Crypto payments
  • Plugin vulnerability
  • Unpatched