CVE-2026-110009: Unzer Payments <= 2.2.1 - Unauthenticated Authentication Bypass to Account Takeover via 'paymentData.email' Parameter

Published Nov 18, 2026
·
Updated

The Unzer Payments plugin for WordPress is vulnerable to Authentication Bypass leading to Account Takeover in all versions up to, and including, 2.2.1. The vulnerability exists because the Google Pay Express Checkout endpoint (/?wc-api=googlepayexpress), handled by startCheckoutDataWithNormalizedCustomerData, accepts an attacker-controlled paymentData.email value and passes it to createOrGetGuestCustomer(), which resolves the submitted email to any existing WordPress user via getuserby('email', ...) and then calls wpsetcurrentuser() and wpsetauthcookie() for the resolved user ID without verifying ownership of the email address, a password, a nonce, an authentication token, or any proof of payment from the payment provider. This makes it possible for unauthenticated attackers to log in as any existing WordPress user — including administrators — by submitting that user's known email address, receiving valid wordpressloggedin session cookies for the targeted account and achieving full site takeover. The endpoint is entirely unprotected with no capability check, nonce validation, or payment-provider signature verification applied, and administrator email addresses are frequently discoverable via the WordPress REST API user enumeration endpoint (/wp-json/wp/v2/users), author archive pages, Gravatar lookups, or site contact footers.

Affected Software

1 affected component
Unzer Unzer Payments for WordPress<=2.2.1

Event History

Nov 18, 2026
CVE Published
via MITRE·01:32 PM
Data Sourced
via MITRE·01:32 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

Any unauthenticated remote attacker can exploit it. The attacker only needs to know the email address of an existing WordPress user; administrator email addresses are explicitly affected.

2

What does an attacker need to provide or bypass?

The affected endpoint accepts an attacker-controlled paymentData.email value and does not require a password, nonce, authentication token, proof of email ownership, payment-provider signature verification, or a capability check.

3

What is the practical impact after successful exploitation?

The attacker receives valid wordpress_logged_in_* session cookies for the account associated with the submitted email address. If that account is an administrator, the attacker can take over the site.

4

How can defenders identify potentially affected installations?

Installations using Unzer Payments for WordPress version 2.2.1 or earlier are affected. The exposed endpoint is available at /?wc-api=google_pay_express and is handled by startCheckoutDataWithNormalizedCustomerData.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203