Safeguard
Vulnerability Analysis•

CVE-2022-43453: High Access Flaw in WP Tools Plugin

CVE-2022-43453 is a high (8.8) missing authorization bug in the WP Tools WordPress plugin up to version 3.41. Update to version 3.43 or later.

Safeguard Security Team
3 min read

CVE-2022-43453 is a high severity (CVSS 8.8) missing authorization flaw in the WP Tools plugin for WordPress, versions up to and including 3.41. Update to 3.43 or later. Check your installed version and apply the update through your normal change process.

What's affected

The record lists WP Tools from Bill Minozzi, from the first release through 3.41. Patchstack gives the patched version as 3.43. Patchstack gives the required privilege as Subscriber.

The record scores it 8.8 (High) with vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Patchstack labels its own priority High. The weakness class is CWE-862 (Missing Authorization).

How to check if you're exposed

Start with an inventory. If you manage the site with WP-CLI, this lists every plugin with its version and whether an update is waiting:

wp plugin list --fields=name,status,version,update

Look for the folder wptools. That folder name comes from the Patchstack entry for this issue, so confirm it matches what sits under wp-content on your site. Without WP-CLI, open the Plugins screen in the dashboard and read the version shown under the name. Version 3.41 or lower is affected. Version 3.43 or later is patched.

Check staging copies, old multisite subsites and inactive plugins too. A deactivated plugin is still on disk, and some of these bugs are reachable through files that load even when the plugin is switched off, so deactivation alone is not a fix. Delete what you do not use.

What to do now

  1. Update WP Tools to 3.43 or a newer release.
  2. After updating, review administrator accounts and recently modified files, since the scoring allows high impact on all three axes.
  3. Review the site's user list and remove accounts you do not recognise.
  4. Turn on automatic updates for the plugin so the next fix lands without a ticket.

Why it matters

An 8.8 score for a plugin bug means the record rates the damage as high on all three axes: confidentiality, integrity and availability. The only thing between an attacker and that impact is a low privilege account. Patchstack lists the lowest role that can trigger it as Subscriber and rates its own priority High, saying such issues tend to be used in mass attack campaigns.

I could not find in the sources what the exposed action does, so I do not describe it. The scoring alone is a good reason to move quickly. A Subscriber account is cheap to get on any site that allows registration.

Note that the Patchstack page lists the patched version as 3.43, not 3.42. Do not stop at a version in between. The record's KEV flag is false, and nothing I fetched reports exploitation in the wild.

Quick check

Why is the score so high?

The record's vector gives high impact on confidentiality, integrity and availability, with only a low privilege requirement and no user interaction.

Is 3.42 safe?

Patchstack lists 3.43 as the patched version, so do not rely on 3.42.

Sources

Safeguard can help you see this across many sites or repositories at once. Paste a manifest into the free in-browser dependency scan at gold.safeguard.sh/scan or look the issue up in the Gold directory to see how the record is tracked.

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.