dbcve.org
Wp 2faWordPress extension · Melapress

CVE-2022-44587

HIGH · 7.5 CVSS v3.1 Published 2024-06-21
Fix available
A fix is available. Upgrade to 2.6.4 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Insertion of Sensitive Information into Log File vulnerability in WP 2FA allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects WP 2FA: from n/a through 2.6.3.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The WP 2FA plugin versions up to 2.6.3 contains a vulnerability allowing sensitive information (likely authentication-related data such as 2FA codes, tokens, or credentials) to be written to log files, combined with improper access control constraints that permit unauthorized access to certain plugin functionality not properly restricted by ACLs.

MitigationUpdate WP 2FA to the latest version beyond 2.6.3 and audit/remediate any log files that may contain exposed sensitive authentication data, ensuring they are purged or secured.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wp 2faWordPress extension
Affected:< 2.6.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify WP 2FA plugin is installed
    In WordPress admin dashboard, go to Plugins > Installed Plugins and look for 'WP 2FA' or 'Melapress Login Security' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'wp-2fa' or similar.
    Affected if The WP 2FA plugin by Melapress is found installed on the WordPress site
  2. Check installed plugin version
    In WordPress admin, click on the WP 2FA plugin to view its details, or check the plugin's main PHP file header for 'Version:' field. Common path: /wp-content/plugins/wp-2fa/wp-2fa.php
    Affected if The displayed version number is less than 2.6.4 (for example, 2.6.3, 2.6.2, etc.)
  3. Identify plugin logging configuration
    In WP 2FA plugin settings (usually under Users > 2FA or the plugin's own settings page), look for a Logging or Debug Log option. Check the plugin folder for any .log files or review the wp-config.php for WP_DEBUG_LOG constant.
    Affected if Logging or debug features are enabled and log files exist in accessible locations
  4. Inspect log file contents and permissions
    Locate any log files in /wp-content/ or /wp-content/uploads/ directories that may contain 'wp-2fa', '2fa', or 'login' in the filename. Use a file manager or FTP to check file permissions and read the file contents to look for authentication tokens, 2FA codes, or credential data.
    Affected if Log files exist and contain sensitive authentication data such as 2FA tokens, backup codes, or user credentials, especially if the files are world-readable

A WordPress site running WP 2FA plugin version below 2.6.4 with logging enabled and exposed log files containing sensitive authentication data indicates the environment is affected by CVE-2022-44587.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.6.4 or later
Fixed in 2.6.4
Interim mitigation

Update WP 2FA to the latest version beyond 2.6.3 and audit/remediate any log files that may contain exposed sensitive authentication data, ensuring they are purged or secured.

Recommended fix High confidence

WP 2FA version 2.6.4

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'WP 2FA' plugin in the list
  4. 4. If an update is available, click 'Update Now' to update to version 2.6.4 or later
  5. 5. Verify the update completed successfully by checking the plugin version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wp 2fa Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-44587 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-44587 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data