sales@hackhalt.com

Home / Threats / CVE-2026-82183

OAuth Single Sign On - Security Vulnerability (CVE-2026-82183)

CVE-2026-82183

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-2026-82183

HIGH CVSS 8.1 Published 2026-09-02 Updated 2026-09-03
AI Risk High (79/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P2 Urgent
Severity Band HIGH
CVSS Vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Affected Components 1
Reference Links 1
AI Risk Engine High (79/100)
Exploitability High
Active Exploitation No strong signal
Published Exploit Status No public exploit references

Threat Timeline

  1. 2026-09-02 CVE published and first recorded in the threat feed.
  2. 2026-09-03 Record updated with latest vulnerability metadata.
  3. 2026-09-04 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 35 days ago

AI enriched 35 days ago (2026-09-04 05:13 UTC)

Technical Summary

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.

Potential Impact

Severity is HIGH (CVSS 8.1). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as High based on low-bar exploit prerequisites.

Primary risk drivers: low-bar exploit prerequisites

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 79/100 (High, High) with priority P2 Urgent. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

OAuth Single Sign On PLUGIN · oauth-single-sign-on Affected: < 7.0.1 Fixed in: 7.0.1

References

What to do about this

Patch promptly The consequence is significant even where an attacker needs a foothold first.

Fix it

Update OAuth Single Sign On to 7.0.1 or later.

That is the complete fix. Everything below is what protects you in the meantime.

No Hack Halt control meaningfully contains this one — updating is the remedy. We would rather say so than sell you something that will not help.

Start free

Not sure if you are affected?

Scan your site to see whether it runs OAuth Single Sign On, and at which version.

Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.

Scan my site free See what Hack Halt does

Am I affected by this vulnerability?

You are affected if your site runs OAuth Single Sign On. Versions below 7.0.1 are vulnerable; that release and later are not. No account is needed to exploit this, so a public site is reachable by anyone.

How do I fix it?

Update OAuth Single Sign On to version 7.0.1 or later. That is the complete fix.