Safeguard
Vulnerability Analysis•

CVE-2022-44587: Medium Log Data Exposure in WP 2FA Plugin

CVE-2022-44587 is a medium (5.3) sensitive information in log file flaw in the WP 2FA WordPress plugin up to 2.6.3. Update to WP 2FA 2.6.4 or later.

Safeguard Security Team
4 min read

CVE-2022-44587 is a medium severity (CVSS 5.3) sensitive information in log file flaw in the WP 2FA plugin for WordPress, versions up to and including 2.6.3. Update to 2.6.4 or later. Check your installed version and apply the update through your normal change process.

What's affected

The record lists WP 2FA from Melapress, from the first release through 2.6.3. Patchstack gives the patched version as 2.6.4. Patchstack gives the required privilege as none, so it is unauthenticated.

The record scores it 5.3 (Medium) with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N. Patchstack labels its own priority Low. The weakness class is CWE-532 (Insertion of Sensitive Information into Log File).

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 wp-2fa. 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 2.6.3 or lower is affected. Version 2.6.4 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 2FA to 2.6.4 or a newer release.
  2. Find any log files the plugin wrote, restrict access to them and remove copies you do not need.
  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

Logs are meant to help operators, but they often end up holding things that should not be written down. This CVE is in that class: the plugin inserts sensitive information into a log file. Patchstack titles it sensitive data exposure via a log file and says an unauthenticated visitor is enough.

For a two factor authentication plugin, a leak in a log is notable even at a medium score, because the plugin deals in material tied to login security. The sources I read do not say exactly what is logged, so I do not claim any particular secret is at risk. The record scores confidentiality impact low and nothing else.

After updating, look at where the plugin keeps log files on your web server and whether they are reachable by URL. Delete old logs you do not need. The record's KEV flag is false, and nothing I fetched reports exploitation in the wild.

Try it yourself

Click through it at your own pace, or open it full screen.

Quick check

What should I do about old log files?

Check whether the plugin wrote logs on your site, restrict web access to that location and delete old copies you do not need, since patching does not remove data already written.

What is the fixed version?

Patchstack lists 2.6.4.

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.