Yaamlabs

Vulnerabilities

No patch for a 10.0 WordPress crypto-plugin flaw

CVE-2026-81648 is a maximum-severity, unpatched flaw in the CryptoPayment Gateway plugin. The plugin is gone from WordPress, so the fix is to remove it.

CryptoPayment Gateway, a WordPress plugin that lets a site take payment in cryptocurrency, has a flaw that anyone can trigger without logging in. It is tracked as CVE-2026-81648, where CVE stands for Common Vulnerabilities and Exposures, the public catalogue number for one specific bug. It scores 10.0 out of 10 on the Common Vulnerability Scoring System (CVSS), the top of the scale. Versions 1.2.1 and 1.2.2 are affected, and 1.2.2 is the last release the author ever shipped.

There is no fix to apply. The plugin was closed on the WordPress Plugin Directory around August 28 over a security issue the directory did not describe, so no newer, safe version exists to update to. It keeps running on an unknown number of sites that already had it installed. The only way to close this is to take the plugin off the site. On top of that, some security trackers report attempts to exploit it, although whether any real site has lost wallet funds is not confirmed.

How the flaw works

WordPress plugins register handlers that the browser can call in the background through one file, wp-admin/admin-ajax.php. The technique is AJAX, short for Asynchronous JavaScript and XML: the browser sends a request carrying an action value, and WordPress routes it to whichever plugin registered that action. A plugin registers each action in one of two ways, one hook for logged-in users and a separate nopriv hook for visitors with no account at all. Putting an administrative action on that second, open path, and then not checking who is calling, is the mistake here.

CryptoPayment Gateway exposed privileged actions on the unauthenticated route and ran them without confirming the caller's identity or permissions. That is a missing authorization flaw, catalogued as CWE-862, where CWE is the Common Weakness Enumeration, a reference list of bug types. It is a form of broken access control: the server does the work for whoever sends the request, logged in or not.

For a payment plugin, that opening reaches the things that matter most. The same handler can read the stored cryptocurrency wallet details, rewrite the gateway's settings and delete files on the server. No password, no account and no interaction from an administrator is needed. An unauthenticated request to a single file is enough, which is why the score sits at the maximum.

What attackers can do, and what is reported

The advisories agree on three things the flaw allows:

  • Wallet credentials in the clear. The plugin stores the keys and addresses that receive customer payments, and the flaw hands them back to an unauthenticated request in readable form. Whoever holds those keys controls the funds that flow to them.
  • Payment settings tampering. An attacker can overwrite the gateway configuration and point future payments at a wallet of their own. This one can outlast the plugin: if the stored settings are left in place, the tampering persists after removal.
  • Arbitrary file deletion. The handler can delete files on the server, which can take the site down or wipe records that would show what happened.

Where the sources split is on real-world use. Defused Cyber reported exploitation attempts beginning on November 2, with the traffic coming from servers sold as "anonymous KYC-free VPS hosting." KYC, Know Your Customer, is the identity check a provider normally runs on a new account; a VPS is a Virtual Private Server, a rented machine. Hosting advertised as skipping the identity check is the kind attackers pick to stay unnamed. Against that, earlier vulnerability-database entries record no confirmed exploitation and note the flaw is not on the Known Exploited Vulnerabilities (KEV) catalogue that the US Cybersecurity and Infrastructure Security Agency keeps. One bulletin claims a private tracker added it to its own KEV list on the same day, but that is a single report.

So the honest reading is this. A public proof-of-concept exists, and at least one firm reports probing traffic. Confirmed theft from a live site has not been published, and the flaw is not on CISA's KEV catalogue. None of that lowers the risk to a site still running the plugin, because the barrier to exploitation is one unauthenticated request. Treat any exposed install as at risk rather than waiting for a confirmed breach.

What to do

Because no patched version exists, removal is the fix, not an interim step.

  1. Remove the plugin. In the WordPress admin, go to Plugins, deactivate CryptoPayment Gateway, then delete it. Deactivating stops its hooks from loading on each request; deleting takes the vulnerable code off the server. Updating is not an option, since 1.2.2 is the final release.
  2. If you cannot remove it this minute, block it at the edge. On a web application firewall (WAF), a filter that sits in front of the site and inspects requests, block unauthenticated POST requests to /wp-admin/admin-ajax.php that carry the plugin's action value, and restrict reaching wp-admin and admin-ajax.php to office or VPN addresses. This narrows the exposure; it does not close the flaw, so still plan the removal.
  3. Rotate the wallet keys and payment credentials the plugin held. Treat anything it stored as disclosed. Generate new wallet keys, move funds to a wallet the old keys cannot reach, and reset any gateway or API secrets the plugin kept.
  4. Check for damage before you move on. Confirm the payout wallet in any remaining payment settings is still yours and was not swapped. Look for administrator accounts you did not create. List files that were deleted or changed around the time of any suspicious traffic.
  5. Review the access logs. Search for POST requests to admin-ajax.php that carry the plugin's action parameter, and pay attention to any coming from hosting-provider ranges you do not recognise. A run of those requests before you removed the plugin is a sign someone reached the handler.

A plugin pulled from the directory is easy to miss. It stops getting updates and shows no warning, yet keeps running exactly as before. Keeping a list of what is installed, and checking it against what is still maintained, is how a closed plugin like this one gets caught before an attacker finds it.

Finding this class of flaw, an endpoint that runs privileged work without an authorization check, is the core of a web application penetration test, and closing the gaps it leaves is the work in safeguarding and hardening. Open the chat and Yaali, our AI agent, will pass your question to the engineer who would do the work.


Sources: Wiz vulnerability database, SentinelOne vulnerability database, OpenCVE, Daily Security Review, Patchstack database.

Back to the blog, or read this post on the full site.