Dev.to Security 🔐 Cybersecurity 👁 0 📖 4 min read

A Checkout Plugin Can Hand a Stranger Your Store's Admin Login. Is It on Your Site?

If your WooCommerce store takes payments through a plugin called Unzer Payments, a new security advisory is worth acting on today. According to a Wordfence advisory published on 18 November 2026, a checkout function in t

If your WooCommerce store takes payments through a plugin called Unzer Payments, a new security advisory is worth acting on today. According to a Wordfence advisory published on 18 November 2026, a checkout function in that plugin can log a visitor in as the matching WordPress user — including the store administrator — using only an email address. No password is required, and the advisory says the plugin does not check that a real payment was made. That would mean full control of the store.

This report comes from a single advisory chain. Wordfence published the details, and public records such as the GitHub Advisory Database and NVD repeat the same wording. As of 19 November 2026, we have not found a second, independent technical investigation or coverage in a news outlet. The facts below are presented as Wordfence describes them.

What happened

Wordfence says the flaw is in Unzer Payments for WooCommerce, in all versions up to and including 2.2.1, and tracks it as CVE-2026-110009, with a critical severity score of 9.8. According to the advisory, the plugin's Google Pay Express Checkout path accepts an email address and then signs the visitor in as the WordPress account that uses that email, administrators included.

Wordfence lists the plugin as unpatched. Its advice is that, with no known fix, it may be best to uninstall the plugin and switch to a replacement. We checked the vendor's public GitHub releases for the same plugin: the latest release shown is still 2.2.1, dated 16 September 2026. We did not find a vendor security notice from Unzer.

None of the official records we reviewed report that this flaw has been used in attacks. A CISA assessment attached to the NVD entry also lists exploitation as none. That can change once a flaw is public, so it is not a reason to wait.

Why this matters if you run a store

"They would need my email" is not much of a barrier. Administrator and shop-manager emails often appear on the public site, in author pages, or in contact details. If the advisory is right, that address alone could be enough to take over the store: change settings, reach customer and order data, or install other software.

WordPress.org does not publish an active-install figure for this plugin (it shows N/A), so there is no reliable number of stores to cite.

Separately, the plugin's page on WordPress.org says it was closed on 11 November 2026 and is not available for download, pending a full review. WordPress.org does not give a reason. That closure should not be treated as confirmation of this advisory, which was published a week later.

What to check today

1. See whether the plugin is installed

In WordPress, open Plugins and look for "Unzer Payments". If you do not manage the site yourself, ask your developer or agency. Also check with anyone who set up checkout, because a payment plugin can be installed and then forgotten.

2. If it is installed, plan a replacement

According to Wordfence, there is no known patch. Do not wait for an update that may not exist yet. Arrange a replacement payment method first so checkout does not simply stop, then deactivate and uninstall Unzer Payments. Take a backup before you change payment plugins, and test checkout afterwards, as in our guide to safe WordPress security updates.

3. Review who can get into the store

If this plugin is, or was, on the site, ask your developer to review administrator and shop-manager accounts, recent logins, and any unexpected users or plugins. Our guide to how to tell if your website has been hacked covers the practical signs. Wordfence has not reported attacks, but a review is still reasonable.

4. See what strangers see

Removing one plugin does not tell you what else the site exposes. A free website security scanner can show what an outsider can see from the internet, without logging in. You can also use the checklist in how to secure a WordPress website.

FAQ

Does this affect every WooCommerce store?

No. According to the advisory, it affects stores that have the Unzer Payments plugin installed, in versions up to 2.2.1. Other payment plugins are a separate question. If you are not sure which checkout plugin you use, check the Plugins screen or ask your developer.

Is there a patch I can install?

Wordfence lists no known patch. The latest public vendor release we found is still 2.2.1. Until a fixed version is published and checked, Wordfence's suggested path is to uninstall the plugin and use a replacement.

If I turn off Google Pay, am I safe?

The advisory does not say whether the affected checkout path is still reachable when that option is switched off in the plugin's settings. Do not assume that a disabled setting is enough. The safer step, according to Wordfence, is to remove the plugin.

Has this been used in attacks?

None of the official records we reviewed report exploitation, and a CISA assessment on the NVD entry lists exploitation as none. That is not a guarantee. Treat it as urgent if the plugin is on your site.

Disclosure: I'm with HackerMe.

📰 Read the original article on Dev.to Security

Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.