PatchTheCVECVE-2022-2083: The Simple Single Sign On WordPress plugin through 4.1.0 leaks its OAuth client_secret, which could be used by
CVE-2022-2083 is a high-severity flaw (CVSS 7.5) affecting simple sign on. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The Simple Single Sign On WordPress plugin through 4.1.0 leaks its OAuth client_secret, which could be used by attackers to gain unauthorized access to the site.
Why this priority
- High severity
- Public exploit reference
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 7.5 (High) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 0.8% (top 44%) |
| CISA exploited list | No |
| Weakness | CWE-319 |
| Published | 2022-09-05 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2022-2083?
simple sign on: upgrade to newer than 4.1.0. Exact commands for each OS are on this page.
Is CVE-2022-2083 being exploited?
CVE-2022-2083 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2022-2083 affect?
CVE-2022-2083 affects simple sign on. Severity is high (CVSS 7.5). The Simple Single Sign On WordPress plugin through 4.1.0 leaks its OAuth client_secret, which could be used by attackers to gain unauthorized access to the site.
How urgent is CVE-2022-2083?
Priority 50/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action