CVE-2023-41873

SAML SP Single Sign On <= 5.0.4 - Missing Authorization to notice dismissal

2023-09-05 00:00
Abdi Pranata

Strategic Overview

Status
Patched in 5.0.5
Affected Plugin
SAML Single Sign On – SSO Login Standard
Affected Version
<= 5.0.4
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2023-41873
View all SAML Single Sign On – SSO Login Standard vulnerabilities

At a glance

CVE-2023-41873 is a medium-severity Missing Authorization vulnerability in the SAML Single Sign On WordPress plugin, affecting versions <= 5.0.4. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 5.0.5; sites on affected versions should update now. Disclosed September 2023, reported by Abdi Pranata.

Vulnerability Overview

The SAML SP Single Sign On plugin for WordPress is vulnerable to unauthorized notice dismissal due to a missing capability check on the close_welcome_modal function in versions up to, and including, 5.0.4. This makes it possible for authenticated attackers, with subscriber-level access and above, to dismiss the welcome tour 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 interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in SAML Single Sign On <= 5.0.4 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For SAML Single Sign On the fix is 5.0.5: builds <= 5.0.4 are affected, anything from 5.0.5 onward is not.

Remediation

Update to version 5.0.5, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: SAML Single Sign On 5.0.5 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-41873https://www.wordfence.com/threat-intel/vulnerabilities/id/c3114906-fac1-42b9-9ba1-0a5d44c2fb3ahttps://nvd.nist.gov/vuln/detail/CVE-2023-41873

Related records

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