CVE-2026-82183

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

2026-08-31 00:00

Strategic Overview

Status: Patched in 7.0.1
Affected Plugin: OAuth Single Sign On – SSO (OAuth Client)
Affected Version: <= 7.0.0
CVSS: 7.3High
Weakness type: CWE-287 · Improper Authentication
CVE: CVE-2026-82183

View all OAuth Single Sign On – SSO (OAuth Client) vulnerabilities

At a glance

CVE-2026-82183 is a high-severity Improper Authentication vulnerability in the OAuth Single Sign On WordPress plugin, affecting versions <= 7.0.0. It carries a CVSS score of 7.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 7.0.1; sites on affected versions should update now. Disclosed August 2026, reported by Pedro Pinho.

Vulnerability Overview

The OAuth Single Sign On – SSO (OAuth Client) plugin for WordPress is vulnerable to account takeover in all versions up to, and including, 7.0.0. This is due to a lack of identify verification. This makes it possible for unauthenticated attackers to takeover non-admin user accounts.

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.0.0 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.0.1: builds <= 7.0.0 are affected, anything from 7.0.1 onward is not.

Remediation

Update to version 7.0.1, 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.0.1 closes this, and updating the plugin is the step that ends it.

Login Security
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-82183 https://www.wordfence.com/threat-intel/vulnerabilities/id/68e395c1-f63d-4c7c-a41f-680f385554e8 https://nvd.nist.gov/vuln/detail/CVE-2026-82183

Related records

Same weakness class

Other vulnerabilities in OAuth Single Sign On – SSO (OAuth Client)

CVSS Vector

7.3

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityLow
IntegrityLow
AvailabilityLow

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/