Most security alerts end with “update to the fixed version”. This one does not. Confection WordPress Cable, versions 0.4.0 to 0.4.7, lets an attacker run their own PHP code on the site without logging in. There is no patched version, and WordPress.org closed the plugin on 23 October 2026. Few sites run it, but if one of your client sites does, it needs your attention today. Here is how to check in two minutes and what to do.
What the flaw is
- Plugin and versions: Confection WordPress Cable 0.4.0 to 0.4.7. No fixed version exists.
- Type: missing authorization and code injection. The plugin saves its settings without checking who sends them, and writes the value straight into a PHP file that the server then runs.
- Severity: CVSS 10.0. No login and no user action needed.
- Exploitation: WPScan lists it as actively exploited.
- Status on WordPress.org: closed since 23 October 2026, pending a full review. The last release is about three years old. Closed plugins get no updates through the dashboard.
Check a site in two minutes
- In wp-admin, open Plugins and search for “Confection”. Note whether it is active and which version it shows.
- Or with WP-CLI:
wp plugin list --fields=name,status,version | grep -i confection
If it is installed, check whether PHP files in its folder changed recently. A recent change you did not make is a warning sign:
find wp-content/plugins/ -path "*confection*" -name "*.php" -mtime -30 -ls
What to do now
- Take a backup first, so you can compare later if you need to.
- Deactivate and delete the plugin. Deactivating alone is not enough when the plugin wrote a PHP file that the server can still reach.
- Need what it did? Look for a maintained alternative. Do not wait for a fix: the plugin has had no release in years.
- Signs of compromise (changed PHP files, unknown admin users, odd redirects)? Take the site offline, restore a backup from before the problem, then rotate the salts, all admin passwords and the database password. Deleting one file is not a clean-up.
- Tell the client in plain words what you removed and why. Most of them will be glad you caught it.
The wider lesson: closed plugins
A closed plugin is the quiet risk on many client sites. It stays installed, it stays active, and the dashboard shows no update, so it looks fine. Once a month, check every site for plugins that are closed on WordPress.org or have had no release for two years or more. Replace them before a flaw like this one turns up, not after.
How Verploy helps
Verploy matches known vulnerabilities to the exact plugin versions on each client site and groups them per vulnerability, so you see in one list which sites run an affected plugin. Every update is checked. Risky ones tested on a copy first. Where no fix exists, as here, the decision is yours: Verploy shows you where to act.
Source: WPScan advisory for CVE-2026-115252, published 9 November 2026; WordPress.org plugin directory, checked 10 November 2026.
Want to see which client sites run a vulnerable plugin, in one list?
Every update is checked, and the risky ones are tested on a copy first. Start free, no credit card.