HomeWordPress vulnerabilitiesOAuth Single Sign On
OAuth Single Sign On vulnerabilities
OAuth Single Sign On has 7 known vulnerabilities in this database. The most recent published record is dated 2 Sep 2026.
- Known vulnerabilities
- 7
- Active installs
- 6,000+
- Latest version
- 7.1.3
- Last updated
- 24 Sep 2026
- Most recent
- 2 Sep 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Authentication bypass CVE-2026-82183 | High 8.1 | Before 7.0.1 | Fixed in 7.0.1 | 2 Sep 2026 |
| Broken access control CVE-2025-10753 | Medium 5.3 | Up to 6.26.14 | Fixed in a later version (latest 7.1.3) | 6 Feb 2026 |
| Security weakness CVE-2025-9485 | Critical 9.8 | Up to 6.26.12 | Fixed in a later version (latest 7.1.3) | 4 Oct 2025 |
| Cross-site request forgery (CSRF) CVE-2025-10752 | Medium 4.3 | Up to 6.26.12 | Fixed in a later version (latest 7.1.3) | 26 Sep 2025 |
| Authentication bypass CVE-2024-10111 | High 8.1 | Up to 6.26.3 | Fixed in a later version (latest 7.1.3) | 12 Dec 2024 |
| Cross-site request forgery (CSRF) CVE-2023-1093 | Medium 6.5 | Before 6.24.2 | Fixed in 6.24.2 | 27 Mar 2023 |
| Authentication bypass CVE-2022-2133 | Medium 5.3 | Before 6.22.6 | Fixed in 6.22.6 | 17 Jul 2022 |
Read the published descriptions
- CVE-2026-82183, 2 Sep 2026
- The OAuth Single Sign On WordPress plugin before 7.0.1 does not verify the identity assertion returned by its Steam single sign-on flow, allowing unauthenticated attackers to log in as an arbitrary non-administrator user, and to create new accounts. CVE record
- CVE-2025-10753, 6 Feb 2026
- The OAuth Single Sign On - SSO (OAuth Client) plugin for WordPress is vulnerable to unauthorized access in all versions up to, and including, 6.26.14. This is due to missing capability checks and authentication verification on the OAuth redirect functionality accessible via the 'oauthredirect' option parameter. This makes it possible for unauthenticated attackers to set the global redirect URL option via the redirect_url parameter granted they can access the site directly. CVE record
- CVE-2025-9485, 4 Oct 2025
- The OAuth Single Sign On - SSO (OAuth Client) plugin for WordPress is vulnerable to Improper Verification of Cryptographic Signature in versions up to, and including, 6.26.12. This is due to the plugin performing unsafe JWT token processing without verification or validation in the `get_resource_owner_from_id_token` function. This makes it possible for unauthenticated attackers to bypass authentication and gain access to any existing user account - including administrators in certain configurations - or to create arbitrary subscriber-level accounts. CVE record
- CVE-2025-10752, 26 Sep 2025
- The OAuth Single Sign On - SSO (OAuth Client) plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 6.26.12. This is due to using a predictable state parameter (base64 encoded app name) without any randomness in the OAuth flow. This makes it possible for unauthenticated attackers to forge OAuth authorization requests and potentially hijack the OAuth flow via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. CVE record
- CVE-2024-10111, 12 Dec 2024
- The OAuth Single Sign On - SSO (OAuth Client) plugin for WordPress is vulnerable to authentication bypass in all versions up to, and including, 6.26.3. This is due to insufficient verification on the user being returned by the social login token. This makes it possible for unauthenticated attackers to log in as any existing user on the site, such as an administrator, if they have access to the username and the user does not have an already-existing account for the service returning the token. CVE record
- CVE-2023-1093, 27 Mar 2023
- The OAuth Single Sign On WordPress plugin before 6.24.2 does not have CSRF checks when discarding Identify providers (IdP), which could allow attackers to make logged in admins delete all IdP via a CSRF attack CVE record
- CVE-2022-2133, 17 Jul 2022
- 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. CVE record
What to do if you run OAuth Single Sign On
If you run OAuth Single Sign On, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new OAuth Single Sign On vulnerabilities
Free. We email you when a new vulnerability is published for OAuth Single Sign On, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.