WordPress plugin · Updated daily · Source: Wordfence Intelligence

OAuth Single Sign On vulnerabilities: affected versions and fixes

OAuth Single Sign On has 6,000+ active installs. Here are its publicly disclosed vulnerabilities, whether your version is affected, and what to do now.

OAuth Single Sign On at a glance

  • 14 publicly disclosed vulnerabilities, 6 of them rated High or Critical. The most recent was disclosed on Nov 4, 2026.
  • Ranked #2674 by popularity on WordPress.org (6,000+ active installs).
  • The latest version is 7.1.5 (released Nov 13, 2026). The most recent security fix shipped in 7.1.4.
  • Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
  • The first thing to do: update to the latest version and turn on automatic updates.

Check your OAuth Single Sign On version

Enter the OAuth Single Sign On version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.

Your version number is compared on this page only. It is not sent anywhere.

Get an email when a new vulnerability is disclosed

We'll tell you when a new vulnerability is disclosed in “OAuth Single Sign On”, with the version that fixes it. Free, email address only, stop any time.

We use your email address only for these alerts. Privacy policy

Want every plugin and theme on your site checked daily?

With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.

View the plugin on wordpress.orgGet a free in-depth scan

How to check whether your site is affected

  1. 1

    Find your version

    In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “OAuth Single Sign On”.

  2. 2

    Compare it with the list below

    If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.

  3. 3

    Update

    Click “Update now” to move to the latest version (7.1.5). Taking a backup first is a good idea.

  4. 4

    Turn on automatic updates

    On the same screen, click “Enable auto-updates” so future fixes are installed automatically.

Known OAuth Single Sign On vulnerabilities

  • OAuth Single Sign On – SSO (OAuth Client) <= 7.1.3 - Unauthenticated Privilege Escalation

    Privilege escalation · CVE-2026-120844

    Affected versions: ≤ 7.1.3

    Fixed in: 7.1.4

    Severity: Critical 9.8 · Disclosed Nov 4, 2026

  • OAuth Single Sign On – SSO (OAuth Client) <= 7.1.2 - Unauthenticated Authentication Bypass

    Missing authorization · CVE-2026-97274

    Affected versions: ≤ 7.1.2

    Fixed in: 7.1.3

    Severity: Medium 5.3 · Disclosed Sep 30, 2026

  • OAuth Single Sign On <= 7.0.0 - Unauthenticated Arbitrary User Account Takeover

    Other weakness · CVE-2026-82183

    Affected versions: ≤ 7.0.0

    Fixed in: 7.0.1

    Severity: High 7.3 · Disclosed Aug 31, 2026

  • OAuth Single Sign On – SSO (OAuth Client) <= 7.0.0 - Missing Authorization

    Missing authorization · CVE-2026-28008

    Affected versions: ≤ 7.0.0

    Fixed in: 7.0.1

    Severity: Medium 5.3 · Disclosed Aug 12, 2026

  • OAuth Single Sign On – SSO (OAuth Client) <= 6.26.14 - Missing Authorization

    Missing authorization · CVE-2025-10753

    Affected versions: ≤ 6.26.14

    Fixed in: 6.26.15

    Severity: Medium 5.3 · Disclosed Feb 5, 2026

  • OAuth Single Sign On – SSO (OAuth Client) <= 6.26.12 - Authentication Bypass via get_resource_owner_from_id_token()

    Missing authorization · CVE-2025-9485

    Affected versions: ≤ 6.26.12

    Fixed in: 6.26.13

    Severity: Critical 9.8 · Disclosed Oct 3, 2025

  • OAuth Single Sign On – SSO (OAuth Client) <= 6.26.12 - Cross-Site Request Forgery

    Cross-site request forgery (CSRF) · CVE-2025-10752

    Affected versions: ≤ 6.26.12

    Fixed in: 6.26.13

    Severity: Medium 4.3 · Disclosed Sep 25, 2025

  • OAuth Single Sign On – SSO (OAuth Client) <= 6.26.3 - Authentication Bypass

    Missing authorization · CVE-2024-10111

    Affected versions: ≤ 6.26.3

    Fixed in: 6.26.4

    Severity: High 8.1 · Disclosed Dec 11, 2024

  • OAuth Single Sign On – SSO (OAuth Client) <= 6.23.3 - Missing Authorization

    Missing authorization · CVE-2022-34155

    Affected versions: ≤ 6.23.3

    Fixed in: 6.23.4

    Severity: High 8.8 · Disclosed May 24, 2023

  • OAuth Single Sign On – SSO (OAuth Client) <= 6.24.1 - Cross-Site Request Forgery via 'delete' in mooauth_client_applist_page

    Cross-site request forgery (CSRF) · CVE-2023-1092

    Affected versions: ≤ 6.24.1

    Fixed in: 6.24.2

    Severity: Medium 4.3 · Disclosed Feb 28, 2023

  • OAuth Single Sign On – SSO (OAuth Client) <= 6.24.1- Cross-Site Request Forgery via 'discard' in mooauth_client_applist_page

    Cross-site request forgery (CSRF) · CVE-2023-1093

    Affected versions: ≤ 6.24.1

    Fixed in: 6.24.2

    Severity: Medium 4.3 · Disclosed Feb 15, 2023

  • OAuth Single Sign On – SSO (OAuth Client) <= 6.22.5 - Authentication Bypass

    Missing authorization · CVE-2022-2133

    Affected versions: ≤ 6.22.5

    Fixed in: 6.22.6

    Severity: High 8.1 · Disclosed Jun 27, 2022

  • OAuth Single Sign On – SSO (OAuth Client) <= 6.22.5 - Cross-Site Scripting

    Cross-site scripting (XSS)

    Affected versions: ≤ 6.22.5

    Fixed in: 6.23.0

    Severity: Medium 6.4 · Disclosed Jun 22, 2022

  • Multiple miniOrange Plugins (Various Version) - Reflected Cross-Site Scripting

    Cross-site scripting (XSS)

    Affected versions: ≤ 6.20.2

    Fixed in: 6.20.3

    Severity: Medium 6.1 · Disclosed Aug 30, 2021

Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Nov 4, 2026.

Most common weaknesses in OAuth Single Sign On

Missing authorization

7 issues

Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.

Cross-site request forgery (CSRF)

3 issues

If an administrator who is logged in opens a booby-trapped page elsewhere, the site can be made to change settings without their knowledge.

Cross-site scripting (XSS)

2 issues

An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.

Frequently asked questions

Is OAuth Single Sign On safe to use?

OAuth Single Sign On is a well-known plugin with 6,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (7.1.5) and turn on automatic updates.

How do I find which version of OAuth Single Sign On my site is running?

In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.

Could updating break my site?

Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.

Can I check all my other plugins too?

Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.

Check every plugin and theme automatically, every day

Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.

Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.

← All plugin vulnerabilitiesOAuth Single Sign On on WordPress.org