CVE-2022-3119: The OAuth client Single Sign On WordPress plugin before 3.0.4 does not have authorisation and CSRF when updati

Q: How do I fix CVE-2022-3119?

oauth client single sign on: upgrade to 3.0.4. Exact commands for each OS are on this page.

Q: Is CVE-2022-3119 being exploited?

CVE-2022-3119 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-3119 affect?

CVE-2022-3119 affects oauth client single sign on. Severity is high (CVSS 7.5). 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,

Q: How urgent is CVE-2022-3119?

Priority 46/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

HIGH 7.5REMOTEUPGRADE

CVE-2022-3119 is a high-severity flaw (CVSS 7.5) affecting oauth client single sign on. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

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.4% (top 61%)
CISA exploited list	No
Weakness	CWE-287, CWE-352
Published	2022-09-26
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: oauth client single sign on project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-09-26 13:15 UTCPublished CVE record published
2026-06-17 04:58 UTCUpdated Record last modified

oauth client single sign on project oauth client single sign on UPGRADE

Affected: < 3.0.4

Fixed in: 3.0.4

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy oauth-client-single-sign-on || rpm -q oauth-client-single-sign-on || oauth-client-single-sign-on --version

2. UPGRADE to 3.0.4 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade oauth-client-single-sign-on

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade oauth-client-single-sign-on

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
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-3119?

oauth client single sign on: upgrade to 3.0.4. Exact commands for each OS are on this page.

Is CVE-2022-3119 being exploited?

CVE-2022-3119 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-3119 affect?

CVE-2022-3119 affects oauth client single sign on. Severity is high (CVSS 7.5). 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,

How urgent is CVE-2022-3119?

Priority 46/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs