OAuth Single Sign On – SSO (OAuth Client) <= 6.22.5 - Cross-Site Scripting

2022-06-22 00:00
Anonymous

Strategic Overview

Status
Patched in 6.23.0
Affected Plugin
OAuth Single Sign On – SSO (OAuth Client)
Affected Version
<= 6.22.5
CVSS
6.4Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE pending
View all OAuth Single Sign On – SSO (OAuth Client) vulnerabilities

At a glance

This record tracks a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the OAuth Single Sign On WordPress plugin, affecting versions <= 6.22.5. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). The issue is fixed in version 6.23.0; sites on affected versions should update now. Disclosed June 2022.

Vulnerability Overview

The OAuth Single Sign On – SSO (OAuth Client) plugin for WordPress is vulnerable to Cross-Site Scripting in versions up to, and including, 6.22.5 due to insufficient input sanitization and output escaping. This makes it possible for attackers to inject arbitrary web scripts that execute in a victim's browser.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Reaching this weakness in OAuth Single Sign On <= 6.22.5 takes a caller who can reach the endpoint. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.

Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For OAuth Single Sign On the fix is 6.23.0: builds <= 6.22.5 are affected, anything from 6.23.0 onward is not.

Remediation

Update to version 6.23.0, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to OAuth Single Sign On: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: OAuth Single Sign On 6.23.0 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/bb2a67ff-a452-4ecb-9fd7-bf05fe43a2f7

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C