# CVE-2025-7045: Cloud SAML SSO <= 1.0.19 - Missing Authorization to Unauthenticated Identity Provider Deletion via delete_config Action

> Unauthenticated attackers can delete Identity Providers in the Cloud SAML SSO plugin, breaking SSO and causing denial of service.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Sep 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-whcq-rh5h-j3wh

## What is CVE-2025-7045?

CVE-2025-7045 is a medium-severity missing authorization vulnerability in cloudinfrastructureservices Cloud SAML SSO – Single Sign On Login, published on 6 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2025-7045?


## How do I fix CVE-2025-7045?

No fix has been published for CVE-2025-7045 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-7045 being exploited?

There is no known exploitation of CVE-2025-7045 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-7045 and fix it if it is affected.

What it is: CVE-2025-7045 is a medium-severity missing authorization vulnerability in cloudinfrastructureservices Cloud SAML SSO – Single Sign On Login, published on 6 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-7045 in the wild and no public exploit code.

Affected product: cloudinfrastructureservices Cloud SAML SSO – Single Sign On Login. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-7045/ (Markdown: https://insights.sbomify.com/CVE-2025-7045/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-7045
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-7045
- OSV: https://osv.dev/vulnerability/CVE-2025-7045

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-7045/
Summaries are generated and may contain mistakes; the official description above is the record.