CVE-2026-110009: Unzer Payments (WordPress plugin) · Improper Authentication
Affects Unzer Payments (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 18 Nov 2026, 13:49 UTC
Thin evidence
One scorer or none| CNA (Wordfence) | CVSS 3.1 | 9.8 |
|---|
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| unzerpluginsUnzer Payments | Affected
| Fixed in– |
Description
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.
References
- wordfence.com/threat-intel/vulnerabilities/id/bcd5a59a-0403-49e6-bbd5-fcbacdc70501?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/unzer-payments/tags/2.2.1/includes/Services/ExpressCheckoutService.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/unzer-payments/tags/2.2.1/includes/Services/ExpressCheckoutService.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/unzer-payments/tags/2.2.1/includes/Services/ExpressCheckoutService.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/unzer-payments/tags/2.2.1/includes/Controllers/ExpressController.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/unzer-payments/tags/2.2.1/includes/Main.php (opens in a new tab)