CVE-2022-3119 OAuth client Single Sign On for WordPress < 3.0.4 - Unauthenticated Settings Update to Authentication Bypass
Unauthenticated attackers can modify OAuth settings to bypass authentication and gain admin access if they know the target email address.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2022-3119?
CVE-2022-3119 is a high-severity missing authorization vulnerability in Unknown OAuth client Single Sign On for WordPress ( OAuth 2.0 SSO ), published on 26 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official 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
Which versions are affected by CVE-2022-3119?
It affects 1 product.
Products include Oauth Client Single Sign on Project Oauth Client Single Sign On.
How do I fix CVE-2022-3119?
No fix has been published for CVE-2022-3119 yet. Limit exposure of the affected software until one is available.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2022-3119 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3119 exists.
Sources
Also known as GHSA-wh77-xq95-gvgr.