CSRF in Oauth Client Single Sign On Project
CVE-2022-3119
- CVSS v3
- 7.5 High
- Public exploits
- None known
- EPSS
- 0.005 · 40.2th percentile
- Published
- 2022-09-26
The OAuth client Single Sign On WordPress plugin before 3.0.4 does not have authorisation and CSRF when updating its settings, which could allow unauthenticated attackers to update them and change the OAuth endpoints to ones they controls, allowing them to then be authenticated as admin if they know the correct email address
Vulnerability class: Broken Authentication
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.5 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N.
- Attack Vector
- Network
AV:N - Attack Complexity
- Low
AC:L - Privileges Required
- None
PR:N - User Interaction
- None
UI:N - Scope
- Unchanged
S:U - Confidentiality
- None
C:N - Integrity
- High
I:H - Availability
- None
A:N
EPSS exploit prediction
EPSS 0.005, 40.2th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
- Oauth Client Single Sign On Project
- Oauth Client Single Sign On For WordPress ( 2.0 Sso ) — versions 3.0.4
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 1 other repository (20142995/nuclei-templates). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- wpscan.com/vulnerability/55b83cee-a8a5-4f9d-a976-a3eed9a558e5 (Exploit, Third Party Advisory)