Skip to main content
CVE-2025-7040VulnerabilityPublished Updated

CVE-2025-7040: Cloud SAML SSO (WordPress plugin) · Missing Authorization

Affects Cloud SAML SSO (WordPress plugin)Source CVE Database V5

0

Not known to be exploited · CVSS 8.2 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
cloudinfrastructureservices Cloud SAML SSO – Single Sign On LoginAffected
  • =0
Fixed in–

AI-suggested

Until a fix is released, restrict access to the plugin's endpoints where possible and monitor for suspicious POST requests targeting organization settings. Applying strict web application firewall (WAF) rules to block unauthorized POST requests to the affected action may help mitigate risk temporarily.

Description

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.

References

Community reviews

Loading reviews…