Cloud SAML SSO <= 1.0.19 - Missing Authorization to Unauthenticated Settings Modification via set_organization_settings Action
Strategic Overview
- Status
- Patched in 1.0.20
- Affected Plugin
- Cloud SAML SSO – Single Sign On Login
- Affected Version
<= 1.0.19- CVSS
- 8.2High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2025-7040
At a glance
CVE-2025-7040 is a high-severity Missing Authorization vulnerability in the Cloud SAML SSO WordPress plugin, affecting versions <= 1.0.19. It carries a CVSS score of 8.2 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires no authentication. The issue is fixed in version 1.0.20; sites on affected versions should update now. Disclosed September 2025, reported by kr0d.
Vulnerability Overview
The Cloud SAML SSO plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'set_organization_settings' action of the csso_handle_actions() function in all versions up to, and including, 1.0.19. The handler reads client-supplied POST parameters for organization settings and passes them directly to update_option() without any check of the user’s capabilities or a CSRF nonce. This makes it possible for unauthenticated attackers to change critical configuration (including toggling signing and encryption), potentially breaking the SSO flow and causing a denial-of-service.
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. A successful exploit has high impact on integrity.
CWE-862: Missing Authorization
Cloud SAML SSO <= 1.0.19 carries this weakness at set_organization_settings, and reaching it takes no account at all. 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 Cloud SAML SSO the fix is 1.0.20: builds <= 1.0.19 are affected, anything from 1.0.20 onward is not.
Remediation
Update to version 1.0.20, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Cloud SAML SSO 1.0.20 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Cloud SAML SSO – Single Sign On Login
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C