Unzer Payments ≤ 2.2.1: An Email Address Is All It Takes to Log In as Admin (CVE-2026-110009, CVSS 9.8)

Running Unzer Payments on your site? Check it against CVE-2026-110009 — free.

The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your Unzer Payments is in the affected range (≤ 2.2.1), it flags it, alongside TLS/HTTPS basics, security headers, cookie flags, exposed files and Firebase/Supabase backend rules. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

Unzer Payments ≤ 2.2.1: An Email Address Is All It Takes to Log In as Admin (CVE-2026-110009, CVSS 9.8)

A checkout endpoint treated a submitted email address as proof of identity — and handed out the matching account's session cookies. That is CVE-2026-110009, an unauthenticated authentication bypass to account takeover in Unzer Payments for WordPress, disclosed November 18, 2026 and rated CVSS 9.8.

What Happened

Unzer Payments offers a Google Pay Express Checkout endpoint (/?wc-api=google_pay_express). Its handler, startCheckoutDataWithNormalizedCustomerData, accepts an attacker-controlled paymentData.email value and passes it to createOrGetGuestCustomer(), which resolves the submitted email to any existing WordPress user via get_user_by('email', ...) — and then calls wp_set_current_user() and wp_set_auth_cookie() for the resolved user ID. No verification of ownership of the email address. No password. No nonce. No authentication token. No proof of payment.

An unauthenticated attacker who submits a known email address receives valid wordpress_logged_in_* session cookies for that account — including administrators — achieving full site takeover. The CVE record notes that administrator emails are frequently discoverable, for example through REST API user enumeration or author archives. The endpoint has no capability check, no nonce validation, and no payment-provider signature verification.

Am I Affected?

Any WooCommerce store running Unzer Payments at 2.2.1 or below with the express checkout in use. Check Plugins in wp-admin, or the plugin's public readme — or run the free check at preshipit.com/free-scan, which reads the version your site announces and flags 2.2.1 and below. A site that discloses no version is reported as unverified, never as vulnerable.

What To Do Now

  1. Update Unzer Payments to the newest available release. This is the fix; everything below is triage while you wait.
  2. Audit users and sessions. The bypass logs the attacker in as a real user through the checkout path, so look for administrator sessions and account activity you cannot tie to a real person or order.
  3. Force a password reset and session invalidation for privileged accounts if an affected version was public. An auth bypass leaves no failed-login trail — the absence of failed logins proves nothing.
  4. Review checkout logs for the express endpoint (/?wc-api=google_pay_express) if your gateway logs it — requests carrying email addresses of your administrators are the signature to look for.

The Bigger Lesson

An email address is an identifier, never a credential. Resolving identity from a submitted email without provider proof — a payment signature, a verified token, a password — is an authentication bypass by design, not by accident. Any endpoint that turns "I know this email" into "I am this user" has already decided that knowing is being. Checkout flows are especially prone to this: they are built to be frictionless for strangers, and frictionless for strangers is exactly the property an attacker needs.

Related: Trust Payments Gateway: A WP_Error Stored as a User ID Becomes an Admin Login — the companion unauthenticated auth bypass in this series, where a checkout error object became an admin login.

Check Unzer Payments on your own site — free.

Our free WordPress Plugin Vulnerability Checker pulls Unzer Payments's current version from wordpress.org and lists the vulnerabilities our scanner checks for — CVE-2026-110009 included. No scan, no account.

Open the free plugin checker →

The PreShipIt Brief — a short weekly email for people shipping vibe-coded apps: the week's important vulnerabilities and launch-safety checks, in plain English.

New and free. Double opt-in: we email you a confirmation link before anything else arrives. Unsubscribe any time.

Running Unzer Payments on your site? Check it against CVE-2026-110009 — free.

The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your Unzer Payments is in the affected range (≤ 2.2.1), it flags it, alongside TLS/HTTPS basics, security headers, cookie flags, exposed files and Firebase/Supabase backend rules. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

← Back home · Run a free mini-scan · Scan my app — $29 · See a sample report