CVE-2025-7045 json
Cloud SAML SSO <= 1.0.19 - Missing Authorization to Unauthenticated Identity Provider Deletion via delete_config Action
published 2025-09-06 14 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-27129
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 35%
- public exploits
- 0
- none known
Summary
The Cloud SAML SSO plugin for WordPress is vulnerable to Identity Provider Deletion due to a missing capability check on the delete_config action of the csso_handle_actions() function in all versions up to, and including, 1.0.19. This makes it possible for unauthenticated attackers to delete any configured IdP, breaking the SSO authentication flow and causing a denial-of-service.
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 14 mo ago
Exploit prediction
0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L |
Affected products
- cloudinfrastructureservices Cloud SAML SSO – Single Sign On Login
Classification
- Weakness
-
- CWE-306 Missing Authentication for Critical Functionality
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/87099513-d8e2-45e5-b7e6-b46558a10d3b?source=cve
- plugins.trac.wordpress.org /browser/cloud-sso-single-sign-on/tags/1.0.19/saml-sso-plugin.php
- wordpress.org /plugins/cloud-sso-single-sign-on/#developers
- plugins.trac.wordpress.org /browser/cloud-sso-single-sign-on/tags/1.0.19/assets/CSSO_Init.php
- plugins.trac.wordpress.org /browser/cloud-sso-single-sign-on/tags/1.0.19/assets/base/CSSO_ActionHandler.php
- plugins.trac.wordpress.org /browser/cloud-sso-single-sign-on/trunk/assets/base/CSSO_ActionHandler.php?rev=3354459#L130
Sources
- CVE List CVE-2025-7045
- NVD CVE-2025-7045
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.