NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🛡️
Not in CISA KEV
CRITICAL severity

CVE-2026-110009 — WordPress

CRITICAL

CVE-2026-110009 is a critical-severity (CVSS 9.8) Improper Authentication vulnerability. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

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…

Published
Updated
Affected
—
Patched
—
Exploits
None indexed
Exploitation data as of Nov 18, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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.

Detection & mitigation playbook

Vulnerability
  1. Detect

    Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

  2. Remediation status

    The records we use list no fixed release for CVE-2026-110009. Check the upstream advisory for a patched version, and apply the exposure-reduction steps below in the meantime.

  3. Mitigate without a patch

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

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 resolve
O3 Security · Impact-Aware SCA

Is CVE-2026-110009 in your dependencies?

Find it across your dependency tree, including transitive dependencies.