Safeguard
Vulnerability Analysis•

CVE-2022-44581: Medium Data Exposure in Defender Security

CVE-2022-44581 is a medium (5.0) insecure storage flaw in the WPMU DEV Defender Security plugin up to 3.3.2. Update to Defender 3.3.3 or later to fix it.

Safeguard Security Team
3 min read

CVE-2022-44581 is a medium severity (CVSS 5.0) insecure storage flaw in the Defender Security plugin for WordPress, versions up to and including 3.3.2. Update to 3.3.3 or later. Check your installed version and apply the update through your normal change process.

What's affected

The record lists Defender Security from WPMU DEV, from the first release through 3.3.2. Patchstack gives the patched version as 3.3.3. Patchstack gives the required privilege as none, so it is unauthenticated.

The record scores it 5.0 (Medium) with vector CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L. Patchstack labels its own priority Low. The weakness class is CWE-922 (Insecure Storage of Sensitive Information).

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 defender-security. 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.3.2 or lower is affected. Version 3.3.3 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 Defender Security to 3.3.3 or a newer release.
  2. Review the site's user list and remove accounts you do not recognise.
  3. Turn on automatic updates for the plugin so the next fix lands without a ticket.

Why it matters

The record describes insecure storage of sensitive information, with the specific variant of sensitive information left in temporary files. In plain terms, the plugin writes something it should have protected to a place other people might read. Defender is a security plugin, so it handles material worth protecting.

Patchstack classes it as broken authentication while the record uses an insecure storage class, and the two sources differ on the privilege needed: Patchstack says none, while the record's vector shows low privileges. If you are unsure, assume an unprivileged visitor could be a starting point.

Neither source says what data ends up exposed. I leave that out. Update and move on. The record's KEV flag is false, and nothing I fetched reports exploitation in the wild.

Quick check

The two sources disagree on privilege. Which is right?

I could not resolve that. The record's vector says a low privilege account is required, and Patchstack lists unauthenticated. Plan for the worse case.

Is the fixed version confirmed?

Patchstack lists 3.3.3.

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.