Hackers Exploit Critical WordPress Plugin Flaw That Exposes Crypto Wallet Credentials in Plain Text
A critical vulnerability with a CVSS score of 10.0 in a popular WordPress crypto payments plugin lets unauthenticated attackers read wallet credentials stored in plain text. The flaw, tracked as CVE-2026-81648, affects the CryptoPayment Gateway plugin for WordPress and WooCommerce, and security researchers say it is already being exploited in the wild.
For store owners who accept crypto at checkout, this is not a theoretical risk. If payment settings can be read by anyone, the credentials controlling incoming payments may already be exposed. Daily coverage like this is tracked on the Zimbuck News page.
What the Vulnerability Actually Does
The flaw affects plugin versions 1.2.1 to 1.2.2. Unauthenticated attackers — anyone on the internet, with no login at all — can read the plugin's payment-gateway settings, including wallet credentials stored in cleartext.
Attackers can also alter gateway configurations and delete random files on the server. Changing a configuration could redirect customer payments to an attacker's wallet, while deleting files can break the site or hide the intrusion. The vulnerability was reported by researcher Pedro Pinho, and WPScan published its disclosure on September 13, 2026.
The full technical reporting is detailed by RS Web Solutions, which summarised the findings from AVES Netsec, its Defused deception network, and WPScan.

Already Exploited in the Wild
What makes this urgent is the exploitation evidence. Security firm AVES Netsec, through its Defused deception network, observed in-the-wild exploitation attempts. Defused posted on November 2, 2026 that there had been no prior public report of in-the-wild exploitation — so these appear to be the first publicly documented abuse of the flaw.
The attempts were traced to servers marketed as "Anonymous KYC-Free VPS Hosting" — infrastructure designed to hide who attackers are, suggesting a planned campaign rather than casual scanning. Merchants discussing this kind of attack traffic share notes in the Zimbuck Market News group.
Which Stores Are at Risk?
The CryptoPayment Gateway plugin lets WooCommerce merchants accept Bitcoin, Bitcoin Cash, Litecoin and Dogecoin directly in their online stores. Any WordPress site running the affected versions — 1.2.1 or 1.2.2 — with crypto checkout enabled should treat this as an emergency check, not a routine update.
Small stores are especially exposed. A large exchange has a security team watching configurations; a small merchant may not check gateway settings for months. If a wallet address was quietly swapped, payments could be diverted long before anyone notices. Our related wallet-security guide How to Check a Token Approval Before You Sign It explains how to check receiving addresses safely, and a second related explainer How to Lock Down Your Crypto Exchange Account covers signs of a compromised checkout.

What Store Owners Should Do Now
Expert Prasen Shelar outlined practical steps for anyone who has used the plugin. The priority is to assume stored credentials may have been seen, verify what your gateway is actually configured to do today, and rotate anything that was stored in the plugin.
- Validate the wallet address in your gateway settings against a secure backup you trust — do not trust the live setting alone
- Monitor for unauthorized alterations to payment configurations, admin accounts and plugin files
- Rotate any stored credentials that were kept in the plugin, including wallet credentials stored in cleartext
- Check your plugin version — if you run versions 1.2.1 to 1.2.2, treat the site as at risk until you have verified it
- Review server files for unexpected deletions or changes that could signal an intrusion
Beyond this one plugin, the lesson is broader. Any tool that stores wallet credentials in plain text creates a single point of failure, and receiving addresses should always be verified from an independent, secure record.
Why This Matters Beyond WordPress
Crypto payments are moving into ordinary e-commerce, bringing ordinary web risks with them. A flaw in a shopping plugin is now, in effect, a flaw in a payments system holding real money — which is why attackers are probing it deliberately. The weakest link is rarely the blockchain itself: Bitcoin, Litecoin and Dogecoin transfers work as designed, but the software wrapped around them, with stored credentials and editable settings, is what attackers target first.
Frequently Asked Questions
Which plugin versions are affected by CVE-2026-81648?
Versions 1.2.1 to 1.2.2 of the CryptoPayment Gateway plugin for WordPress and WooCommerce. The vulnerability carries a critical CVSS score of 10.0 and was disclosed by WPScan on September 13, 2026, following a report by researcher Pedro Pinho.
What can attackers actually do with this flaw?
Without any login, attackers can read payment-gateway settings including wallet credentials stored in cleartext, alter those configurations — potentially redirecting payments — and delete random files on the server.
What should I do if my store used this plugin?
Validate the wallet address in your gateway settings against a secure backup, monitor for unauthorized alterations, and rotate any stored credentials, following the advice attributed to expert Prasen Shelar. Check your version first, and treat affected versions as at risk until verified.
Stay alert, keep your store and wallet settings verified, and join the conversation at zimbuck.com, where the community tracks crypto security news as it breaks. This article is market news and general information only, not financial advice.