CVE-2025-6003 json
WordPress Single Sign-On (SSO) - Multiple Versions - Incorrect Authorization to Sensitive Information Exposure
published last yr. modified 4mo ago also EUVD-2025-18162
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 24%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2025-6003 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.31% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected products
- cyberlord92 WordPress Single Sign-On (SSO) - Single Site Standard
- cyberlord92 WordPress Single Sign-On (SSO) - Single Site Premium
- cyberlord92 WordPress Single Sign-On (SSO) - Multisite Premium
- cyberlord92 WordPress Single Sign-On (SSO) - Single Site Enterprise
- cyberlord92 WordPress Single Sign-On (SSO) - Multisite Enterprise
- cyberlord92 WordPress Single Sign-On (SSO) - Single Site All-Inclusive
- cyberlord92 WordPress Single Sign-On (SSO) - Multisite All-Inclusive
Classification
- Weakness
-
- CWE-863 Incorrect Authorization
- Technology feeds
References
Sources
- CVE List CVE-2025-6003
- NVD CVE-2025-6003
Fencer Intel 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.