CVE-2026-62142
CSRF in WP 2FA plugin allows attackers to change 2FA settings on affected WordPress sites.
Is CVE-2026-62142 being exploited?
Not confirmed. CVE-2026-62142 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.13% probability of exploitation in the next 30 days.
How severe is CVE-2026-62142?
CVE-2026-62142 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-62142?
Not known from our data. No patch reference has been recorded for CVE-2026-62142, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-62142 affect?
CVE-2026-62142 affects Melapress WP 2FA (WP 2FA) <= 4.1.0, WordPress sites using WP 2FA plugin. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-62142?
Update to a fixed plugin release; if unavailable, disable/remove plugin or restrict admin POSTs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
CSRF enables attackers to modify/disable 2FA or change admin settings via forged requests, enabling account takeover or privilege abuse.
Immediate action required
- affected<= 4.1.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.