On this page (7 sections)
A critical flaw, tracked as CVE-2026-110009, affects the Unzer Payments plugin for WordPress in all versions up to and including 2.2.1. According to the GitHub Advisory Database entry, the plugin's Google Pay Express Checkout endpoint can be abused by an unauthenticated visitor to be logged in as an existing user, including an administrator, which means a full site takeover.
If you run a WordPress or WooCommerce store with this plugin installed, treat it as urgent. At the time of writing the advisory lists no patched version, and the research available to us comes from a single advisory chain, so some details remain unconfirmed.
What happened
The advisory was published on November 18, 2026 and describes an authentication bypass that leads to account takeover. The core problem is simple to state: the plugin's express checkout code trusts an email address supplied in the request and signs the matching WordPress user in, without checking that the visitor actually owns that account.
The text of the advisory is identical in the GitHub entry and on NVD, and NVD simply repeats the same description, so this is one source reported twice rather than two independent confirmations. The advisory also references a Wordfence threat intelligence entry and the plugin's 2.2.1 source code on WordPress.org Trac.
Technical details in plain terms
The affected entry point is the Google Pay Express Checkout endpoint, exposed through a WooCommerce API callback (/?wc-api=google_pay_express). According to the advisory, the handler startCheckoutDataWithNormalizedCustomerData takes a paymentData.email value from the request and passes it to createOrGetGuestCustomer(). That function looks up an existing WordPress user by that email with get_user_by('email', ...), then calls wp_set_current_user() and wp_set_auth_cookie() for the user it found.
What is missing is any proof of identity. The advisory says there is no check of email ownership, password, nonce, authentication token, or proof of payment from the payment provider, and no capability check or payment-provider signature verification on the endpoint. In other words, the site hands out a valid logged-in session cookie to whoever asks for it with the right email address.
This is CWE-287, improper authentication: the product accepts a claim of identity without verifying it. The CVSS vector reflects the practical impact: network reachable, low complexity, no privileges, no user interaction, and high impact on confidentiality, integrity and availability.
Why the email requirement is not much protection
An attacker needs to know the email address of the account they want to impersonate. The advisory points out that administrator emails are frequently discoverable through the WordPress REST API user listing (/wp-json/wp/v2/users), author archive pages, Gravatar lookups, or contact details in a site footer. So the email requirement should not be counted on as a barrier.
Who is affected
- Sites with the Unzer Payments plugin installed at version 2.2.1 or earlier. The advisory says all versions up to and including 2.2.1 are affected.
- Stores where the Google Pay Express Checkout feature is part of the plugin. The advisory does not say whether the endpoint is reachable when the feature is disabled in settings, so do not assume a disabled option makes you safe until the vendor confirms it.
- Sites with administrator or shop manager accounts, since a successful login as one of them means full control of the site, according to the advisory.
Whether a fixed release exists is not stated. The GitHub entry lists affected and patched versions as unknown, so check the plugin's page on WordPress.org and the vendor's announcements directly.
How to check your exposure
Start by confirming whether the plugin is installed and which version you run. This WP-CLI command, run from your WordPress root as a user that can read the site, lists the plugin with its status and version. Look for a version of 2.2.1 or lower.
wp plugin list --fields=name,status,version | grep -i unzerNext, look in your web server access logs for requests to the affected endpoint. This grep, run on the server against your access log (adjust the path for your setup), shows requests that include the Google Pay express callback. Legitimate checkouts will appear here too, so look for hits that do not line up with real orders, especially followed by admin-area activity from the same IP address.
grep 'wc-api=google_pay_express' /var/log/nginx/access.logWhat to do now
- Confirm whether Unzer Payments is installed and which version is active, using the WP-CLI command above or the Plugins screen.
- Check the plugin's WordPress.org page and the vendor's channels for a release newer than 2.2.1. If one exists, test and install it promptly.
- If no fixed version is available and you can accept the loss of that payment method, deactivate the plugin until a patch is released. Offer customers another payment option in the meantime.
- Review the user list for administrator and shop manager accounts you do not recognize, and review recent changes such as new users, changed roles, installed plugins and edited theme or plugin files.
- Search access logs for requests to the express checkout endpoint and for unusual admin logins around the same times.
- If you find signs of unauthorized access, change passwords for privileged users, end all active sessions, and rotate the WordPress salts in wp-config.php so existing login cookies stop working.
- Reduce the chance of email discovery by restricting the public user listing and author archives where your site does not need them.
Detection and monitoring afterwards
Because this flaw produces a normal-looking logged-in session, the signs are in what happens next. Watch for new administrator accounts, role changes, plugin or theme installs, modified files, and logins from unfamiliar IP addresses. If you suspect a compromise, follow our guides on how to check if a website is hacked and what to do when a website is hacked.
You can also run a free malware scan for visible signs of injected code, though an outside-in scan cannot see everything inside a server, as explained in what outside-in malware detection can and cannot see. Keep tracking this CVE: once a fixed version is named, update and record the date you did so.
To make checking your other plugins a routine habit, see our guide on how to tell whether a WordPress plugin is vulnerable.
What is and is not known
| Question | Status |
|---|---|
| Is the flaw real and described by a CVE? | Yes, CVE-2026-110009, published November 18, 2026 |
| Severity | CVSS 9.8, critical, per the GitHub Advisory Database and NVD |
| Affected versions | All up to and including 2.2.1 |
| Patched version | Not stated in the advisory |
| Exploitation in the wild | Not reported in the research; unconfirmed |
| Independent confirmation | Limited: NVD repeats the GitHub text |
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.
