CVE-2022-4496

SAML Single Sign On – SSO Login Premium Multisite < 20.0.7 - Open Redirect

2023-01-06 00:00
Harsh Tiwari

Strategic Overview

Status
Patched in 16.0.8
Affected Version
16 – < 16.0.8
CVSS
6.1Medium
Weakness type
CWE-601 · URL Redirection to Untrusted Site ('Open Redirect')
CVE
CVE-2022-4496
View all SAML Single Sign On – SSO Login Standard vulnerabilities

At a glance

CVE-2022-4496 is a medium-severity URL Redirection to Untrusted Site ('Open Redirect') vulnerability in the SAML Single Sign On WordPress plugin, affecting versions 16 – < 16.0.8. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 16.0.8; sites on affected versions should update now. Disclosed January 2023, reported by Harsh Tiwari.

Vulnerability Overview

The SSO Login Premium Multisite plugin for WordPress is vulnerable to Open Redirect in versions up to, and including, 20.0.7 due to missing validation of its redirect parameter. This makes it possible for an attacker to redirect authenticated users. This vulnerability also affects the Premium Edition (versions <12.1.0) and Standard Edition (versions <16.0.8) of the plugin.

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 privileges on the target site.

CWE-601: URL Redirection to Untrusted Site ('Open Redirect')

Reaching this weakness in SAML Single Sign On 16 – < 16.0.8 takes a caller who can reach the endpoint. An open redirect is a page that takes a destination from the request and sends the browser there without checking that the destination belongs to the site.

A link that starts on a trusted domain finishes on an attacker's, which is what makes phishing and consent-screen abuse credible to the person clicking it. For SAML Single Sign On the fix is 16.0.8: builds 16 – < 16.0.8 are affected, anything from 16.0.8 onward is not.

Remediation

Update to version 16.0.8, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

Related records

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