WordPress Single Sign-On (SSO) - Multisite Premium <= 38.5.8 - Missing Authorization
Strategic Overview
- Status
- Patched in 38.5.8.1
- Affected Plugin
- WordPress Single Sign-On (SSO) - Multisite Enterprise
- Affected Version
<= 38.5.8- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-57807
At a glance
CVE-2026-57807 is a medium-severity Missing Authorization vulnerability in the WordPress Single Sign-On (SSO) - Multisite Enterprise WordPress plugin, affecting versions <= 38.5.8. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 38.5.8.1; sites on affected versions should update now. Disclosed July 2026, reported by Kim Dvash.
Vulnerability Overview
The WordPress Single Sign-On (SSO) - Multisite Enterprise plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on a function in all versions up to, and including, 38.5.8. This makes it possible for unauthenticated attackers to perform an unauthorized action.
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, and no interaction from a victim user.
CWE-862: Missing Authorization
Reaching this weakness in WordPress Single Sign-On (SSO) - Multisite Enterprise <= 38.5.8 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 WordPress Single Sign-On (SSO) - Multisite Enterprise the fix is 38.5.8.1: builds <= 38.5.8 are affected, anything from 38.5.8.1 onward is not.
Remediation
Update to version 38.5.8.1, 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: WordPress Single Sign-On (SSO) - Multisite Enterprise 38.5.8.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in WordPress Single Sign-On (SSO) - Multisite Enterprise
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C