CVE-2022-3119

Public Exploit
OAuth client Single Sign On for WordPress < 3.0.4 - Unauthenticated Settings Update to Authentication Bypass

Description

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

Category

7.5
CVSS
Severity: High
CVSS 3.1 •
EPSS 0.07%
Third-Party Advisory wpscan.com
Affected: Unknown OAuth client Single Sign On for WordPress ( OAuth 2.0 SSO )
Published at:
Updated at:

References

Link Tags
https://wpscan.com/vulnerability/55b83cee-a8a5-4f9d-a976-a3eed9a558e5 third party advisory exploit

Frequently Asked Questions

What is the severity of CVE-2022-3119?
CVE-2022-3119 has been scored as a high severity vulnerability.
How to fix CVE-2022-3119?
To fix CVE-2022-3119, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2022-3119 being actively exploited in the wild?
It is possible that CVE-2022-3119 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2022-3119?
CVE-2022-3119 affects Unknown OAuth client Single Sign On for WordPress ( OAuth 2.0 SSO ).
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.