On the disclosure of CVE-2026-110009, the NVD assigned a CVSS v3.1 base score of 9.8 (CRITICAL) with a network-attack vector to an authentication bypass vulnerability in the Unzer Payments plugin for WordPress. Every version up to and including 2.2.1 is affected. If your organization operates a WooCommerce storefront with this plugin installed and the Google Pay Express Checkout feature reachable, an unauthenticated remote attacker can take over any WordPress account on the site — including administrators — by simply knowing or guessing the target's email address.
This is not a theoretical weakness buried in a code path nobody touches. The vulnerable endpoint is a payment checkout handler designed to be reachable by unauthenticated shoppers, which means the attack surface is exposed to the internet by design. No credentials, no session, no social engineering required. In my 15 years of incident response work, authentication bypasses of this class in WordPress plugins consistently become mass-exploitation events within days of public disclosure. Treat this as an emergency patch cycle.
Technical Analysis
Affected Products and Versions
| Component | Affected Versions | Platform |
|---|---|---|
| Unzer Payments plugin for WordPress | All versions ≤ 2.2.1 | WordPress with WooCommerce |
Vulnerability Details
- CVE ID: CVE-2026-110009
- CVSS 3.1: 9.8 (CRITICAL) — Vector: Network / Low complexity / No privileges required / No user interaction
- Vulnerability Type: Authentication Bypass → Account Takeover (CWE-288 / CWE-305 class weakness)
- Advisory: NVD — CVE-2026-110009
Attack Chain (Defender's View)
The vulnerable code path works as follows:
- The plugin registers a WooCommerce API endpoint:
GET/POST /?wc-api=google_pay_express(the Google Pay Express Checkout handler). - This endpoint is processed by the function
startCheckoutDataWithNormalizedCustomerData, which accepts Google PaypaymentDatasupplied by the client. - Critically, the function trusts the attacker-controlled value
paymentData.emailwithout verifying that the requester controls the Google account associated with that email — no token validation against Google's servers is performed on this path before the email is consumed. - The submitted email is passed to
createOrGetGuestCustomer(), which calls WordPress core'sget_user_by('email', ...). - If a user with that email exists (administrator, shop manager, customer — any role), the plugin calls
wp_set_current_user()followed bywp_set_auth_cookie(). The response then carries a valid, authenticated WordPress session cookie for the victim account, issued to the attacker.
The exploitation requirement is trivially low: the attacker only needs to know the email address of a target account. Administrator emails are frequently discoverable via site metadata, WHOIS, prior breach corpora, or author archive enumeration (/?author=1 redirects). Once an attacker holds an admin session, full site compromise follows: plugin/theme upload, web shell deployment, database access, customer PII theft, payment-skimmer injection (Magecart-style), and pivoting into connected infrastructure.
Exploitation Status
At time of writing, the vulnerability has been published to NVD with a complete technical root-cause description, which materially lowers the bar for exploit development. The endpoint path, the vulnerable function names, and the exact parameter (paymentData.email) are all public. Defenders should assume weaponization is imminent or already underway and verify CISA KEV listing status daily. There is no legitimate reason for unauthenticated requests to this endpoint to specify an email belonging to a registered, privileged user — which gives defenders a clean high-fidelity detection hook.
Detection & Response
The highest-fidelity signal is HTTP access to the wc-api=google_pay_express endpoint itself — particularly from unusual source IPs, at unusual volume (enumeration behavior), or followed by authenticated administrative actions from the same source. Web server and WAF logs are your primary telemetry; endpoint rules should focus on post-compromise behavior (unexpected plugin/theme changes, new admin users, web shells written to wp-content).
---
title: Unzer Payments Google Pay Express Endpoint Access — Potential CVE-2026-110009 Exploitation
id: 3f8c1d2a-9b44-4e67-a1c5-7d2e8f901ab3
status: experimental
description: Detects HTTP requests to the Unzer Payments plugin Google Pay Express Checkout endpoint associated with CVE-2026-110009 authentication bypass. Requests to this unauthenticated endpoint should be rare and originate from legitimate customer sessions; bursts or access from hosting/VPN infrastructure are strongly suspicious.
references:
- https://nvd.nist.gov/vuln/detail/CVE-2026-110009
author: Security Arsenal
date: 2026/04/06
tags:
- attack.initial_access
- attack.t1190
logsource:
category: webserver
detection:
selection_uri:
cs-uri-query|contains: 'wc-api=google_pay_express'
filter_method_head:
cs-method: 'HEAD'
condition: selection_uri and not filter_method_head
falsepositives:
- Legitimate customer Google Pay Express checkout activity
- Payment gateway health checks
level: high
---
title: WordPress Administrator Activity Following Google Pay Express Endpoint Access
id: 8e2a5f71-4c39-4b8d-9e12-6a7f3d250c91
status: experimental
description: Correlates access to the vulnerable Unzer Google Pay Express endpoint with subsequent requests to WordPress administrative surfaces (wp-admin, plugin/theme upload, user creation) from the same source address, consistent with CVE-2026-110009 account takeover followed by post-exploitation.
references:
- https://nvd.nist.gov/vuln/detail/CVE-2026-110009
author: Security Arsenal
date: 2026/04/06
tags:
- attack.initial_access
- attack.privilege_escalation
- attack.t1190
- attack.t1078
logsource:
category: webserver
detection:
selection_endpoint:
cs-uri-query|contains: 'wc-api=google_pay_express'
selection_admin:
cs-uri-stem|contains:
- '/wp-admin/admin-post.php'
- '/wp-admin/user-new.php'
- '/wp-admin/plugin-install.php'
- '/wp-admin/theme-install.php'
- '/wp-admin/update.php'
- '/wp-json/wp/v2/users'
condition: selection_endpoint or selection_admin
falsepositives:
- Administrators legitimately managing the site from the same IP used for testing checkout
level: medium
---
title: Web Shell or PHP File Written Under WordPress Content Directory
id: 61c9d4e8-2f7a-4b5c-83d1-9e4a6b0f52c7
status: experimental
description: Detects creation of PHP files in WordPress upload or content directories by the web server process, a common post-exploitation artifact following WordPress administrative account takeover via vulnerabilities such as CVE-2026-110009.
references:
- https://nvd.nist.gov/vuln/detail/CVE-2026-110009
author: Security Arsenal
date: 2026/04/06
tags:
- attack.persistence
- attack.t1505.003
logsource:
category: file_event
product: linux
detection:
selection_path:
TargetFilename|contains:
- '/wp-content/uploads/'
- '/wp-content/plugins/'
- '/wp-content/themes/'
- '/wp-content/mu-plugins/'
selection_ext:
TargetFilename|endswith:
- '.php'
- '.phtml'
- '.phar'
filter_known_writers:
TargetFilename|contains:
- '/wp-content/uploads/sites/'
condition: selection_path and selection_ext
falsepositives:
- Legitimate plugin/theme installations or updates by administrators
- Some backup or caching plugins writing PHP stubs
level: high
// Hunt for requests to the vulnerable Unzer Google Pay Express endpoint
// and correlate with subsequent administrative activity from the same source.
// Assumes web server / WAF logs ingested via CommonSecurityLog (CEF) or custom web log table.
let Lookback = 14d;
let ExploitRequests =
CommonSecurityLog
| where TimeGenerated > ago(Lookback)
| where RequestURL has "wc-api=google_pay_express"
| project EndpointTime=TimeGenerated, SourceIP, RequestURL, RequestMethod, HttpUserAgentOriginal, DeviceAction;
ExploitRequests;
// Correlation: sources that hit the endpoint AND then touched wp-admin user/plugin surfaces
let SuspiciousSources = ExploitRequests | distinct SourceIP;
CommonSecurityLog
| where TimeGenerated > ago(Lookback)
| where SourceIP in (SuspiciousSources)
| where RequestURL has_any ("/wp-admin/user-new.php", "/wp-admin/plugin-install.php",
"/wp-admin/theme-install.php", "/wp-admin/update.php", "/wp-json/wp/v2/users")
| project TimeGenerated, SourceIP, RequestURL, RequestMethod, HttpUserAgentOriginal
| order by SourceIP, TimeGenerated asc;
// Enumeration behavior: sources hitting the endpoint at high frequency (email guessing)
ExploitRequests
| summarize RequestCount=count(), FirstSeen=min(EndpointTime), LastSeen=max(EndpointTime) by SourceIP, HttpUserAgentOriginal
| where RequestCount > 5
| order by RequestCount desc;
-- Hunt a Linux web host for post-exploitation artifacts consistent with
-- WordPress admin takeover via CVE-2026-110009:
-- recently created PHP files under wp-content (potential web shells).
LET wp_roots = glob(glob='/var/www/*/wp-content/**/*.php')
+ glob(glob='/var/www/html/**/wp-content/**/*.php')
+ glob(glob='/srv/www/**/wp-content/**/*.php')
SELECT FullPath, Size, Mtime, Ctime,
read_file(filename=FullPath, length=4096) AS HeadBytes
FROM foreach(row=wp_roots)
WHERE Mtime > now() - 7*24*3600
AND (
HeadBytes =~ 'eval\\s*\\(|base64_decode|gzinflate|shell_exec|passthru|\\$_(GET|POST|REQUEST|COOKIE)\\['
OR FullPath =~ 'wp-content/uploads/.*\\.php$'
)
ORDER BY Mtime DESC
#!/usr/bin/env bash
# CVE-2026-110009 — Unzer Payments plugin verify / mitigate script
# Run on the WordPress host (adjust WP_PATH / WP_CLI as needed).
WP_PATH="/var/www/html"
WP_CLI="/usr/local/bin/wp"
echo "=== [1] Identify Unzer Payments plugin version ==="
$WP_CLI plugin list --path="$WP_PATH" --format=table | grep -i unzer || echo "Unzer plugin not found."
PLUGIN_DIR="$WP_PATH/wp-content/plugins"
UNZER_DIR=$(find "$PLUGIN_DIR" -maxdepth 1 -iname '*unzer*' -type d 2>/dev/null | head -n1)
if [ -n "$UNZER_DIR" ]; then
echo "=== Installed version (from plugin header) ==="
grep -m1 -i 'Version:' "$UNZER_DIR"/unzer-payments.php "$UNZER_DIR"/*.php 2>/dev/null | head -n3
echo "=== [2] Update plugin to latest patched release (>= fixed version from vendor) ==="
$WP_CLI plugin update --path="$WP_PATH" --all --format=summary | grep -i unzer || true
echo "=== [3] Emergency workaround if patching is not immediately possible ==="
echo "Blocking the vulnerable endpoint at the web server layer."
echo "--- Add to nginx server block: ---"
cat <<'NGINX'
location ~* "wc-api=google_pay_express" {
return 403;
}
NGINX
echo "--- Or add to Apache/.htaccess: ---"
cat <<'HTACCESS'
RewriteCond %{QUERY_STRING} wc-api=google_pay_express [NC]
RewriteRule ^ - [F,L]
HTACCESS
echo "=== [4] Hunt access logs for exploitation attempts ==="
for log in /var/log/nginx/access.log /var/log/apache2/access.log /var/log/httpd/access_log; do
[ -f "$log" ] || continue
echo "--- $log ---"
grep -E 'wc-api=google_pay_express' "$log" | awk '{print $1}' | sort | uniq -c | sort -rn | head -n20
done
echo "=== [5] Review administrator accounts for unauthorized additions ==="
$WP_CLI user list --path="$WP_PATH" --role=administrator \
--fields=ID,user_login,user_email,user_registered --format=table
else
echo "Unzer plugin directory not found under $PLUGIN_DIR — verify install path."
fi
echo "=== Done. Rotate all admin credentials and WordPress salts if suspicious hits were found. ==="
Remediation
- Patch immediately. Update the Unzer Payments plugin to the latest release that supersedes version 2.2.1. Verify the fixed version number against the official Unzer plugin changelog on wordpress.org/plugins or the vendor advisory referenced in the NVD entry for CVE-2026-110009. Do not rely on "latest" alone — confirm the version string post-update.
- If you cannot patch within hours, block the endpoint. The endpoint
/?wc-api=google_pay_expressis the single exploitation vector. A WAF rule, nginxlocationblock, or Apache rewrite rule returning 403 for any request whose query string containswc-api=google_pay_expressneutralizes the vulnerability without affecting standard WooCommerce checkout (only Google Pay Express checkout is impacted). - Audit for compromise before and after patching. Patching does not evict an attacker who already holds a session or has created persistence. Specifically:
- Review access logs for requests containing
wc-api=google_pay_express, with attention to repeated requests (email enumeration) and source IPs that subsequently accessed/wp-admin/. - Audit all administrator and shop-manager accounts (
wp user list --role=administrator) for unauthorized additions, and checkwp_users/wp_usermetafor role escalations. - Inspect
wp-contentfor recently modified or anomalous PHP files (the VQL hunt above automates this). - Review installed plugins/themes against a known-good baseline.
- Review access logs for requests containing
- If any suspicious activity is found, assume full compromise. Rotate all WordPress credentials (all privileged users, not just suspected victims), invalidate all sessions by regenerating the authentication keys and salts in
wp-config.php, rotate database credentials and any API keys stored in wp-config or plugin settings (including Unzer/PSP API credentials), and initiate a formal incident response process. - Reduce future blast radius. Enforce MFA on all wp-admin accounts (an attacker-issued auth cookie bypasses login-time MFA, so pair this with application-password and session-management controls), restrict
/wp-admin/by IP allowlist or VPN where operationally feasible, disable unused payment express-checkout features, and ensure WooCommerce and all plugins are on an automated update cadence. - Monitor CISA KEV. Track whether CVE-2026-110009 is added to the CISA Known Exploited Vulnerabilities catalog, which would impose binding remediation deadlines for federal civilian agencies and signal confirmed in-the-wild exploitation for everyone else.
The pattern here — a payment plugin trusting client-supplied identity claims and converting them directly into an authenticated session via wp_set_auth_cookie() — is one of the most dangerous WordPress vulnerability classes. Network-reachable, unauthenticated, CVSS 9.8, and trivially exploitable with public root-cause details. Patch today, hunt this week.
Related Resources
Security Arsenal Penetration Testing Services AlertMonitor Platform Book a SOC Assessment vulnerability-management Intel Hub
Is your security operations ready?
Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.