Good to knowVulnerabilities

The CryptoPayment Gateway WordPress plugin has a maximum-severity flaw and no known fix. Press reports attacks. Remove it if you run it

CVE-2026-81648 (CVSS 10) lets anyone on the internet, without logging in, delete files, overwrite the payment settings and read stored wallet credentials on sites running CryptoPayment Gateway 1.2.1 or 1.2.2. WPScan lists no fix. The Hacker News reports exploitation attempts on 3 Nov 2026. What it is, who is affected and what to do.

Updated 3 Nov 2026: see what changed

How urgent

Good to know

Who is affected

WordPress sites running the CryptoPayment Gateway plugin (slug cryptopayment-gateway), versions 1.2.1 and 1.2.2. WPScan lists no fixed version

What to do

If you run this plugin, deactivate and remove it now and use a maintained payment option. Then check for deleted or changed files and unexpected changes to the payment settings, and move funds to a new wallet and rotate any keys the plugin stored

Published 3 Nov 2026 · Sources last checked 3 Nov 2026No. 42 / 87

Updates, follow-ups and corrections

  1. Update · 3 Nov 2026. The plugin is no longer in the official WordPress plugin directory: its page says it was closed on 28 Aug 2026 for a security issue and is not available for download. That confirms there is no maintained version to update to, so removing it remains the only fix. A Brazilian security account also says the wallet credentials are stored in plain text and that the attack attempts come from anonymous hosting; we could not verify either claim, so treat the credentials as readable anyway.

We keep the original text. When something changes, when we follow a story, or when we get something wrong, we add a dated note here instead of editing silently.

What it is

CVE-2026-81648 affects the CryptoPayment Gateway plugin for WordPress, versions 1.2.1 and 1.2.2. According to the WPScan advisory, one of the plugin's AJAX endpoints does not check who is calling it. That lets an anonymous visitor perform administrator actions: delete arbitrary files on the server, overwrite the payment gateway settings, and recover the wallet credentials the plugin stores. The CVSSCVSS score A number from 0 to 10 that rates how serious a flaw is in general. From 9.0 up it is called Critical. Tap again to open the glossary score is 10.0, the maximum.

Fix status

WPScan lists the fix as "No known fix". The advisory was published on 10 September 2026 and the CVECVE A public ID number, like CVE-2026-12345, given to one specific security flaw so everyone can talk about the same bug. Tap again to open the glossary record on 13 September. We did not find a patched version.

Is it being attacked?

The Hacker News reported on 3 November 2026 that attackers are trying to exploitExploit A piece of code or a technique that takes advantage of a specific flaw to get something the attacker should not get. Tap again to open the glossary the flaw, citing findings from the firm Defused Cyber. We could not open that article or find Defused Cyber's own report, so we cannot say how widespread the attempts are. The CVE record shows the flaw is not in CISA's Known Exploited VulnerabilitiesVulnerability A weakness in software, a setting or a process that an attacker could use to get in or do harm. Tap again to open the glossary catalog, and its exploitation-probability score is low (about 0.5%). Treat the press report as a warning that this is worth acting on, not as a measure of how many sites have been hit.

What to do

Our advice, based on the advisory:

  1. Check if you use it: in WordPress, Plugins, look for CryptoPayment Gateway and its version.
  2. If you do, deactivate and delete it. With no fix, updating is not an option. Switch to a payment option that is actively maintained.
  3. Look for damage: files missing from the site, changed payment settings, and unusual requests to admin-ajax.php in your server logs.
  4. Assume the stored wallet credentials may have been read: if the plugin held keys or API credentials, move funds to a new wallet and rotate those credentials. Check your wallet's recent transactions.
  5. If you do not use WordPress for payments, there is nothing to do.

What we could not confirm

We read the WPScan advisory and the CVE record. We could not read The Hacker News article or Defused Cyber's report, so the exploitation claim comes from a press headline and summary only. We do not know who maintains the plugin, whether the author has been told, or whether any site has lost funds. Versions below 1.2.1 are not listed as affected, but we did not check them.

Comments

No account needed. Add a nickname if you like, or leave it empty to comment anonymously. Comments are reviewed before they appear. Links are not allowed.

    We store your comment, your nickname and a scrambled form of your connection that we use only to limit spam. We do not store your IP address or set cookies. Cloudflare Turnstile checks that you are not a bot.

    Sources and verification

    We use primary sources first and say when we rely on a news report. Dates are the day we last checked each source.

    Spotted a mistake? Email [email protected] and we will correct it and note the change.

    Get the free runbooks

    One-page security checklists for founders who build with AI. You get a confirmation email first, then the runbooks.

    Send me the runbooks