CVE-2022-3631: The OAuth Client by DigitialPixies WordPress plugin through 1.1.0 does not sanitize and escapes some of its se

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

oauth client: upgrade to newer than 1.1.0. Exact commands for each OS are on this page.

Q: Is CVE-2022-3631 being exploited?

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

CVE-2022-3631 affects oauth client. Severity is medium (CVSS 4.8). The OAuth Client by DigitialPixies WordPress plugin through 1.1.0 does not sanitize and escapes some of its settings, which could allow high-privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfilter

Q: How urgent is CVE-2022-3631?

Priority 33/100. Public exploit reference

Routine

MEDIUM 4.8UPGRADE

CVE-2022-3631 is a medium-severity flaw (CVSS 4.8) affecting oauth client. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The OAuth Client by DigitialPixies WordPress plugin through 1.1.0 does not sanitize and escapes some of its settings, which could allow high-privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example, in multisite setup).

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	4.8 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	High
User interaction	Required
EPSS exploit chance	0.5% (top 54%)
CISA exploited list	No
Weakness	CWE-79
Published	2022-11-14
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: digitialpixies

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

Am I affected?

Timeline

2022-11-14 15:15 UTCPublished CVE record published
2026-06-17 04:59 UTCUpdated Record last modified

digitialpixies oauth client UPGRADE

Affected: <= 1.1.0

Fixed in: newer than 1.1.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy oauth-client || rpm -q oauth-client || oauth-client --version

2. UPGRADE to newer than 1.1.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade oauth-client

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade oauth-client

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-3631?

oauth client: upgrade to newer than 1.1.0. Exact commands for each OS are on this page.

Is CVE-2022-3631 being exploited?

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

CVE-2022-3631 affects oauth client. Severity is medium (CVSS 4.8). The OAuth Client by DigitialPixies WordPress plugin through 1.1.0 does not sanitize and escapes some of its settings, which could allow high-privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfilter

How urgent is CVE-2022-3631?

Priority 33/100. Public exploit reference

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2022-3632 MEDIUM 6.5 UPGRADE The OAuth Client by DigitialPixies WordPress plugin through 1.1.0 does not have CSRF checks in some places, wh

References

← Back to latest CVEs