CVE-2026-110009 json
Unzer Payments <= 2.2.1 - Unauthenticated Authentication Bypass to Account Takeover via 'paymentData.email' Parameter
published 13h ago modified 3h ago also EUVD-2026-128851
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
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=google_pay_express`), 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 `get_user_by('email', ...)` and then calls `wp_set_current_user()` and `wp_set_auth_cookie()` 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 `wordpress_logged_in_*` 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.
Is CVE-2026-110009 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- unzerplugins Unzer Payments
Classification
- Weakness
-
- CWE-287 Improper Authentication
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/bcd5a59a-0403-49e6-bbd5-fcbacdc70501?source=cve
- plugins.trac.wordpress.org /browser/unzer-payments/tags/2.2.1/includes/Services/ExpressCheckoutService.php#L163
- plugins.trac.wordpress.org /browser/unzer-payments/tags/2.2.1/includes/Services/ExpressCheckoutService.php#L49
- plugins.trac.wordpress.org /browser/unzer-payments/tags/2.2.1/includes/Services/ExpressCheckoutService.php#L246
- plugins.trac.wordpress.org /browser/unzer-payments/tags/2.2.1/includes/Controllers/ExpressController.php#L173
- plugins.trac.wordpress.org /browser/unzer-payments/tags/2.2.1/includes/Main.php#L96
Sources
- CVE List CVE-2026-110009
- NVD CVE-2026-110009
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.