GHSA-CQ6V-QCF9-9MF3
Vulnerability from github – Published: 2026-11-18 15:34 – Updated: 2026-11-18 15:34The 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.
{
"affected": [],
"aliases": [
"CVE-2026-110009"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-11-18T14:17:25Z",
"severity": "CRITICAL"
},
"details": "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(\u0027email\u0027, ...)` 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 \u2014 including administrators \u2014 by submitting that user\u0027s 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.",
"id": "GHSA-cq6v-qcf9-9mf3",
"modified": "2026-11-18T15:34:33Z",
"published": "2026-11-18T15:34:33Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-110009"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/unzer-payments/tags/2.2.1/includes/Controllers/ExpressController.php#L173"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/unzer-payments/tags/2.2.1/includes/Main.php#L96"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/unzer-payments/tags/2.2.1/includes/Services/ExpressCheckoutService.php#L163"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/unzer-payments/tags/2.2.1/includes/Services/ExpressCheckoutService.php#L246"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/unzer-payments/tags/2.2.1/includes/Services/ExpressCheckoutService.php#L49"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/bcd5a59a-0403-49e6-bbd5-fcbacdc70501?source=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.