CVE-2026-97274

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

2026-09-30 00:00
rpgsec

Strategic Overview

Status
Patched in 7.1.3
Affected Version
<= 7.1.2
CVSS
5.3Medium
Weakness type
CWE-287 · Improper Authentication
CVE
CVE-2026-97274
View all OAuth Single Sign On – SSO (OAuth Client) vulnerabilities

At a glance

CVE-2026-97274 is a medium-severity Improper Authentication vulnerability in the OAuth Single Sign On WordPress plugin, affecting versions <= 7.1.2. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 7.1.3; sites on affected versions should update now. Disclosed September 2026, reported by rpgsec.

Vulnerability Overview

The OAuth Single Sign On – SSO (OAuth Client) plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 7.1.2. This is due to missing enforcement of the email-verification claim when the claim is absent from the IdP response, because the old inline check was gated on isset($resource_owner[$idp_email_verified_key]) and skipped silently when the claim was not present. This makes it possible for unauthenticated attackers to gain access to an account without a verified email address by authenticating through an OAuth provider that omits the email-verification claim from its response, causing the verification check to be silently bypassed. The 'email verified' check must be enabled in the plugin settings (mo_oauth_email_verify_check).

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-287: Improper Authentication

Reaching this weakness in OAuth Single Sign On <= 7.1.2 takes no account at all. Improper authentication means the mechanism that proves who a caller is can be satisfied without the secret it was supposed to require.

An attacker authenticates as another user — administrators included — without ever knowing a password, so password policies and login rate limits never come into play. For OAuth Single Sign On the fix is 7.1.3: builds <= 7.1.2 are affected, anything from 7.1.3 onward is not.

Remediation

Update to version 7.1.3, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: OAuth Single Sign On 7.1.3 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C