# CVE-2025-6003: WordPress Single Sign-On (SSO) - Multiple Versions - Incorrect Authorization to Sensitive Information Exposure

> Unauthenticated attackers can extract sensitive restricted site content due to incorrect authorization checks in the WordPress Single Sign-On plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jun 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-p4cv-qgmg-7q4w

## What is CVE-2025-6003?

CVE-2025-6003 is a medium-severity missing authorization vulnerability in cyberlord92 WordPress Single Sign-On (SSO) - Multisite All-Inclusive, published on 12 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WordPress Single Sign-On (SSO) plugin for WordPress is vulnerable to unauthorized access due to a misconfigured capability check on a function in all versions up to, and including, the *.5.3 versions of the plugin. This makes it possible for unauthenticated attackers to extract sensitive data including site content that has been restricted to certain users and/or roles.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2025-6003 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-6003 is a medium-severity missing authorization vulnerability in cyberlord92 WordPress Single Sign-On (SSO) - Multisite All-Inclusive, published on 12 Jun 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-6003 in the wild and no public exploit code.

Affected product: cyberlord92 WordPress Single Sign-On (SSO) - Multisite All-Inclusive. 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-6003/ (Markdown: https://insights.sbomify.com/CVE-2025-6003/index.md)
```

## Sources

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

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