OAuth client Single Sign On for WordPress ( OAuth 2.0 SSO ) vulnerabilities
Plugin slug oauth-client-for-user-authentication · 2 known vulnerabilities · latest disclosed 2022-08-23 · WordPress.org page
Every listed vulnerability has a fix. Version 3.0.4 or later is not affected by any of them. If your site runs an older version, update it.
2 of 2 rated high or critical (CVSS 7 or more).
Known vulnerabilities in OAuth client Single Sign On for WordPress ( OAuth 2.0 SSO )
| Severity | Affected versions | Fixed in | CVE | Published | Details |
|---|---|---|---|---|---|
| High 7.3 | <= 3.0.3 | 3.0.4 | CVE-2022-3119 | 2022-08-23 | Advisory |
| High 7.2 | <= 3.0.1 | 3.0.2 | none | 2022-05-03 | Advisory |
Check if a site is affected
Enter a site address to see which version of OAuth client Single Sign On for WordPress ( OAuth 2.0 SSO ) and other plugins it runs, and whether they match a known vulnerability.
Questions
Is the OAuth client Single Sign On for WordPress ( OAuth 2.0 SSO ) plugin safe to use?
All 2 known issues are fixed in current versions (3.0.4 or later). Keeping it updated is what matters.
How do I check which version of OAuth client Single Sign On for WordPress ( OAuth 2.0 SSO ) my site runs?
In WordPress go to Plugins > Installed Plugins. From the outside, the free PluginPeek scan below reads the version from the site's public files.
How do I fix a vulnerable plugin?
Make a full backup, then update it from Dashboard > Updates and check the site afterwards. If you would rather not, we can do it for a fixed $99, paid after you have checked the site.