CSRF in Oauth Client Single Sign On Project
CVE-2022-3119
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.
EPSS exploit prediction
EPSS: 0.004 (36.3th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 36th percentile — 36.3% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.004 · newest: 0.004 · change: +0.000
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 proof-of-concept exploits
References
- wpscan.com/vulnerability/55b83cee-a8a5-4f9d-a976-a3eed9a558e5 (Exploit, Third Party Advisory)
Frequently asked questions
- What is CVE-2022-3119?
- CVE-2022-3119 is a high-severity vulnerability in Oauth Client Single Sign On Project, classified under Improper Authentication. CVSS score: 7.5/10. Published 2022-09-26.
- How severe is CVE-2022-3119?
- High severity. CVSS v3 base score is 7.5 out of 10.
- Is CVE-2022-3119 known to be exploited?
- 1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.