WordPress WP 2FA plugin <= 2.6.3 - Sensitive Data Exposure via Log File vulnerability

published 2024-06-21 2 y ago modified 2026-06-17 4 mo ago also EUVD-2022-47525

cvss: 5.3; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 38%
public exploits: 0; none known

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.

Patch / fix

fixed in 2

melapress wp_2fa 2.6.4
wpwhitesecurity wp_2fa 2.6.4

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: partial
Assessed: 2 y ago (2024-06-25)

Exploit prediction

0.44% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	5.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected products

melapress wp_2fa

Classification

Weakness

CWE-532 Insertion of Sensitive Information into Log File

Technology feeds

WordPress rss critical rss

References

patchstack.com /database/vulnerability/wp-2fa/wordpress-wp-2fa-plugin-2-6-3-sensitive-data-exposure-via-log-file-vulnerabilit
vdb-entry, third-party-advisory

Sources

CVE List CVE-2022-44587
NVD CVE-2022-44587

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.

Summary