CVE
Unzer Payments authentication bypass in Google Pay checkout
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
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.
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.8, total technical impact per CISA
- No patch5/5No patch listed yet
What would change the score
- Would score about 80 if added to CISA KEV
- Would score about 75 if CISA's SSVC rates exploitation active
- Would score about 40 if advisories confirm default setups are exposed
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-110009 (Unzer Payments <= 2.2.1 - Unauthenticated Authentication Bypass to Account Takeover via 'paymentData.email' Parameter), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-110009 (entry last updated 2026-11-18):
Affected:
- unzerplugins Unzer Payments: through 2.2.1
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-110009 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-110009 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/bcd5a59a-0403-49e6-bbd5-fcbacdc70501?source=cve
- https://plugins.trac.wordpress.org/browser/unzer-payments/tags/2.2.1/includes/Services/ExpressCheckoutService.php#L163
- https://plugins.trac.wordpress.org/browser/unzer-payments/tags/2.2.1/includes/Services/ExpressCheckoutService.php#L49
- https://plugins.trac.wordpress.org/browser/unzer-payments/tags/2.2.1/includes/Services/ExpressCheckoutService.php#L246
- https://plugins.trac.wordpress.org/browser/unzer-payments/tags/2.2.1/includes/Controllers/ExpressController.php#L173
- https://plugins.trac.wordpress.org/browser/unzer-payments/tags/2.2.1/includes/Main.php#L96
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-110009
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-110009"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- unzerplugins Unzer Payments
through 2.2.1
Evidence 8
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-110009
Is CVE-2026-110009 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-110009?
Unzer Payments: through 2.2.1.Source: cve.now feed data