WordPress plugin
OAuth client Single Sign On for WordPress ( OAuth 2.0 SSO ) security & vulnerabilities
No known unpatched vulnerabilities in the latest version
All 2 known vulnerabilities are fixed in the latest release. If you run an older version, update to null or newer.
- Critical0
- High2
- Medium0
- Low0
All OAuth client Single Sign On for WordPress ( OAuth 2.0 SSO ) vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| High7.3 | Missing Authorization ≤3.0.3Update to 3.0.4 | CVE-2022-3119 | |
| High7.2 | Cross-Site Scripting ≤3.0.1Update to 3.0.2 | — |
- High7.3Missing Authorization
≤3.0.3Update to 3.0.4
- High7.2Cross-Site Scripting
≤3.0.1Update to 3.0.2
OAuth client Single Sign On for WordPress ( OAuth 2.0 SSO ): common questions
Does OAuth client Single Sign On for WordPress ( OAuth 2.0 SSO ) have known vulnerabilities?
Yes. VulnCrest Radar lists 2 known vulnerabilities in OAuth client Single Sign On for WordPress ( OAuth 2.0 SSO ): 2 high. None are known to affect version null.
How do I check which version of OAuth client Single Sign On for WordPress ( OAuth 2.0 SSO ) I run?
In wp-admin open Plugins → Installed Plugins; the version is shown under the name. Without admin access, our passive Check my site tool can often read it from public files.
What is the most recent OAuth client Single Sign On for WordPress ( OAuth 2.0 SSO ) vulnerability?
CVE-2022-3119, published Aug 23, 2022: OAuth client Single Sign On for WordPress ( OAuth 2.0 SSO ) <= 3.0.3 - Missing Authorization. Severity: High (CVSS 7.3).
Is any OAuth client Single Sign On for WordPress ( OAuth 2.0 SSO ) vulnerability listed in CISA KEV?
No. None of the known OAuth client Single Sign On for WordPress ( OAuth 2.0 SSO ) vulnerabilities is currently listed in the CISA KEV catalog.