CVE-2022-2891 json
WP 2FA < 2.3.0 - Time-Based Side-Channel Attack
published 4y ago modified 4mo ago also EUVD-2022-35120
- cvss
- 5.9
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 62%
- public exploits
- 0
- none known
Summary
The WP 2FA WordPress plugin before 2.3.0 uses comparison operators that don't mitigate time-based attacks, which could be abused to leak information about the authentication codes being compared.
Patch / fix
- Unknown WP 2FA 2.3.0
Is CVE-2022-2891 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.97% chance of exploitation in the next 30 days, higher than 62% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- wpscan.com https://wpscan.com/vulnerability/301b3dce-2584-46ec-92ed-1c0626522120 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected products
- Unknown WP 2FA
Classification
- Weakness
-
- CWE-203 Observable Discrepancy
- Technology feeds
References
-
wpscan.com
/vulnerability/301b3dce-2584-46ec-92ed-1c0626522120
exploit, vdb-entry, technical-description, third-party-advisory
Sources
- CVE List CVE-2022-2891
- NVD CVE-2022-2891
Fencer Intel 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.