
By Samuel Torres — Software & Cloud Engineer. 23+ production sites.
Nearly every WordPress security guide ends with the same word: update. That works as long as there is a newer version. The trouble starts when you open the advisory and the "patched version" field is empty. According to LayerOps' count of Wordfence Intelligence data, 652 new WordPress vulnerabilities were published between 1 and 16 November 2026; as of 16 November, 61 (9%) had no patched version listed and 181 (28%) were rated high or critical.
This guide is for that 9%: how to find closed or abandoned plugins, how to block the attack while there is no fix, and how to replace a payment plugin without taking the store down. It is what I would do on a WooCommerce store.
The Unzer Payments case: admin login with just an email
This month's example is Unzer Payments for WooCommerce, a payment gateway plugin. CVE-2026-110009, issued by Wordfence as the CNA and published on 18 November 2026, covers all versions up to and including 2.2.1 and carries a CVSS score of 9.8 (critical).
The flaw sits in the Google Pay Express Checkout endpoint (/?wc-api=google_pay_express). It takes an email address, looks up the WordPress user with that email and logs them in: no password, no nonce, no proof that a payment happened. With the administrator's email, the attacker is the administrator. The record notes those addresses are often discoverable through author pages, Gravatar or the site footer.
What happened next is the interesting part:
- HackerMe reported on 19 November that Wordfence listed the plugin as unpatched and that WordPress.org had closed it on 11 November, with no download available pending review.
- Patchstack's entry from 18 November said "No official patch available".
- On 20 November, while I was writing this, the plugin page on WordPress.org was back with version 2.2.2 (updated 20 November at 9:43 GMT), whose changelog reads "Critical security fix for Google Pay Express Checkout".
Version 2.2.2 targets exactly the vulnerable feature, but when I checked, Patchstack had not yet marked it as the patched version and the CVE record still listed only the affected range. That gap of hours or days between "there is a new release" and "it is confirmed to fix the issue" is part of the problem. And from 11 to 20 November, anyone running this plugin had nothing to update to. That scenario is what this article is about.
Step 1: list your plugins and find the closed ones
wp plugin list tells you what you have and whether an update exists. It does not tell you whether WordPress.org closed the plugin. A closed plugin gets no updates, so it shows "no update available", which is not the same as "all good".
cd /home/usuario/public_html
wp plugin list --fields=name,status,version,update,update_version --format=table
To check whether any of them is closed, ask the public plugin directory API. For a closed plugin the response contains "error":"closed" and the closure date:
#!/bin/bash
# Check each installed plugin's status on WordPress.org
cd /home/usuario/public_html
for slug in $(wp plugin list --field=name); do
r=$(curl -s "https://api.wordpress.org/plugins/info/1.2/?action=plugin_information&request%5Bslug%5D=$slug")
if echo "$r" | grep -q '"error":"closed"'; then
echo "CLOSED: $slug -> $(echo "$r" | grep -o '"closed_date":"[^"]*"')"
elif echo "$r" | grep -q '"error"'; then
echo "NOT ON WORDPRESS.ORG: $slug (premium or custom: check it by hand)"
else
echo "ok: $slug -> $(echo "$r" | grep -o '"last_updated":"[^"]*"')"
fi
done
What it tells you:
- Closed. On the web, the plugin page shows "This plugin has been closed". It can be temporary (a security review) or permanent. While it is closed, there are no updates through the directory.
- Abandoned.
last_updatedshows the date of the last release. If it has gone years without changes and it touches payments, users or files, review it. - Outside the directory. Premium and custom plugins don't show up in the API. For those you rely on the vendor's notices and the vulnerability databases.
Then cross-check the list against a vulnerability database: Wordfence Intelligence, Patchstack or WPScan. Search by plugin slug and look at the patched-version field. If it says there is none, you are in the situation this article covers.
Step 2: mitigate while there is no patch
With no fixed version, you have three levers, from the safest to the most surgical.
Deactivate the plugin if you can live without it
It is the only mitigation that doesn't depend on guessing the attack vector correctly. If you have another gateway active, run on that one for a few days:
wp plugin deactivate unzer-payments
Once deactivated, its code isn't loaded. Back up first, and check that checkout still offers at least one payment method.
Block only the affected feature
If you can't switch off the whole plugin, block the exact route the advisory names. For Unzer it is the wc-api=google_pay_express endpoint. On Apache (cPanel), at the top of the account's .htaccess:
# Temporary mitigation CVE-2026-110009 (Unzer Payments <= 2.2.1)
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{QUERY_STRING} (^|&)wc-api=google_pay_express(&|$) [NC]
RewriteRule ^ - [F]
RewriteRule ^wc-api/google_pay_express - [NC,F]
</IfModule>
The second rule covers the pretty-permalink form (/wc-api/…), which WooCommerce also accepts. The side effect is obvious: Google Pay Express stops working. I would rather lose one payment button for a few days than lose the admin account.
If the site sits behind Cloudflare, you can stop the request before it reaches the server with a WAF custom rule set to Block:
(lower(http.request.uri.query) contains "google_pay_express") or (lower(http.request.uri.path) contains "/wc-api/google_pay_express")
Back up .htaccess and test on staging: a syntax error there returns a 500 on the whole site.
The vendor's WAF rule
Patchstack says on its Unzer entry that it issued a mitigation rule, and Wordfence ships firewall rules for some vulnerabilities. Check whether your plan gets that rule, but treat it as one more layer, not as a replacement for the measures above.
Limit what the attacker gains
Check how many administrators you have (wp user list --role=administrator) and whether their email addresses are public anywhere on the site: in the Unzer case, the attacker needs that address. If you care about the customer-account side, I cover it in Black Friday account theft.
Step 3: replace a payment plugin without taking the store down
If the plugin is still unpatched or has been closed for good, replace it. With a payment gateway, that has more moving parts than it looks.
- Pick the official replacement. Look for the plugin published by the payment provider itself, or an alternative gateway with an official, actively maintained plugin in the directory. Avoid third-party forks with no track record.
- Full backup. Database and files, and make sure you know how to restore them (command below).
- Staging with real data. Clone the store, install the replacement and set it up with the provider's test (sandbox) credentials.
- A complete test order. Purchase, approved payment, declined payment, customer email, order status change and refund.
- Check what depends on the old gateway. Saved cards, subscriptions and refunds on past orders are usually tied to the gateway that charged them. Before deleting the old plugin, decide how you will refund those orders (usually from the provider's dashboard).
- Change window. Do it in your slowest sales hour, with the new provider already approved for live payments. Activate it, place a small real order and refund it.
- Written rollback. If the real order fails, reactivating the previous gateway should be one command, not an investigation. If the old one is the vulnerable one, the rollback goes together with the block from Step 2.
- Afterwards, remove the old plugin (
wp plugin delete), don't just deactivate it: vulnerable code on disk is still a risk if something loads it again.
The supporting commands for the backup and for checking which payment methods are active before and after the switch:
cd /home/usuario/public_html
# Database backup before touching the gateway
wp db export /home/usuario/respaldos/before-gateway.sql
# Payment methods and whether they are enabled
wp wc payment_gateway list --user=1 --fields=id,title,enabled --format=table
Back up and test every one of these steps on staging before touching production.
Not everything is Unzer: when a fix does exist
The same week brought advisories for far more common plugins, and there the answer really is to update:
- Elementor: WPSec published on 17 November 2026 a sensitive information exposure (CVSS 4.3, medium) in versions 3.28.0 through 4.4.0. Contributor-level users and above could see titles, authors and links of drafts and private posts. Fix: update to 4.4.1 or later.
- Search & Replace: Patchstack published on 18 November 2026 a privilege escalation to super admin on multisite (CVE-2026-107740, CVSS 7.2) in versions before 3.2.4. It requires an administrator account. Fix: 3.2.4.
In those two cases updating closes the issue; with Unzer, for days, it wasn't an option. That is why your plugin review has to read the patched-version field, not just the alert headline.
The real case
I don't have a documented case involving Unzer Payments or a closed plugin on the sites I run, and I'm not going to make one up.
What I do have is the method. I run 23+ production WordPress sites on AlmaLinux + WHM/cPanel and migrated 61 domains to PHP 8.3 one at a time, with backup and rollback. For an unpatched plugin I would do the same: run the Step 1 script on every account, separate the ones with the affected plugin, apply the block on one, confirm checkout still takes payments through the other methods, and then move on to the rest.
What I wouldn't do
I wouldn't leave a closed plugin installed "because it still works". Working and being fixed are different things.
I wouldn't install a copy of the plugin downloaded from some other site "to get the latest version". It has no more guarantees than the official one, and usually fewer.
I wouldn't hand-edit the plugin's code except as a temporary, documented patch: the next update wipes it without warning.
And I wouldn't call the case closed just because a new version shipped: keep the block in place until a vulnerability database marks that version as patched.
Let's review it together
If you don't know how many of your plugins are closed, abandoned or unpatched, that is the first thing I check in a WordPress security audit. If you'd rather have someone watch it every week, there is maintenance. Write to me through the contact page and we'll go over it.
Sources
- 652 new vulnerabilities from 1 to 16 November 2026; 61 (9%) with no patched version; 181 (28%) high or critical: LayerOps' count of Wordfence Intelligence data, layerops.tech/wordpress-vulnerabilities. Original database: Wordfence Intelligence.
- Unzer Payments, CVE-2026-110009: versions up to 2.2.1, CVSS 9.8,
google_pay_expressendpoint, published 18 November 2026, CNA Wordfence: CVE record and Wordfence Intelligence advisory. - Unzer Payments with no official patch, and mitigation rule: Patchstack.
- Unzer Payments closed on WordPress.org on 11 November 2026 and listed as unpatched by Wordfence (as of 19 November): HackerMe on DEV.
- Unzer Payments 2.2.2 of 20 November 2026 and its changelog: WordPress.org.
- Elementor up to 4.4.0, CVSS 4.3, fixed in 4.4.1: WPSec WPSEC-2026-3290.
- Search & Replace before 3.2.4, CVE-2026-107740, CVSS 7.2: Patchstack.
- Plugin API response for a closed plugin: WordPress.org API.
About the author
Samuel Torres is a Software & Cloud Engineer at Conqr Digital Agency (Mexico City). He runs 23+ production WordPress sites and processed 80,000 documents with OCR + LLM. More at /en/about. Get a quote on WhatsApp in 2 min



