SAML Single Sign On – SAML SSO Login <= 4.8.75 - Cross-Site Request Forgery

2019-05-20 00:00
Anonymous

Strategic Overview

Status
Patched in 4.8.76
Affected Plugin
SAML Single Sign On – SSO Login
Affected Version
<= 4.8.75
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE pending
View all SAML Single Sign On – SSO Login vulnerabilities

At a glance

This record tracks a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the SAML Single Sign On WordPress plugin, affecting versions <= 4.8.75. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 4.8.76; sites on affected versions should update now. Disclosed May 2019.

Vulnerability Overview

The SAML Single Sign On plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 4.8.75. This is due to missing or incorrect nonce validation. This makes it possible for unauthenticated attackers to gain otherwise restricted access to administrative actions via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in SAML Single Sign On <= 4.8.75 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For SAML Single Sign On the fix is 4.8.76: builds <= 4.8.75 are affected, anything from 4.8.76 onward is not.

Remediation

Update to version 4.8.76, 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 4.8.76 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/10e49bdd-3a72-4bb7-ba31-21ba4a5b377f

Related records

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