smart-sso through 2.0.1 Incorrect Authorization in PermissionFilter Enables Admin Escalation
Affects smart-sso 2.0.1 and earlier in the default dev Spring profile, where admin REST paths under /admin/** are not registered and so get no access control. Fixed in 2.0.2.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.0.2
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected product is smart-sso through version 2.0.1. Default dev Spring profile configuration (the out-of-the-box configuration). Admin REST paths under /admin/** are not registered in permission data, so PermissionFilter permits them when the path is not configured.
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity9.7/10CVSS 8.7, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 25 if CISA's SSVC rates it automatable
CVE-2026-121543 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects smart-sso; fixed in 2.0.2.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 18/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 2.0.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
The smart-sso authentication software is affected by an authorization flaw in its permission filter that lets any logged-in user reach administrator functions. An attacker with a normal account could grant themselves admin rights, reset passwords, and manage users, roles, and connected applications.
Read the original description
smart-sso through 2.0.1 contains an incorrect authorization vulnerability in PermissionFilter that allows any authenticated user to call admin console APIs because unlisted paths are permitted by default. Attackers can call /admin/user-role/save to assign themselves the administrator role, reset passwords, and manage users, roles, and applications across integrated systems.
What to do
Check whether your setup matches what the bug needs.
Affected product is smart-sso through version 2.0.1. Default dev Spring profile configuration (the out-of-the-box configuration). Admin REST paths under /admin/** are not registered in permission data, so PermissionFilter permits them when the path is not configured.Upgrade to a fixed version: 2.0.2.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- a466350665 smart-sso
through 2.0.1
Evidence 7
- Patch
- Patch
- Report
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-121543
Is CVE-2026-121543 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Any authenticated account on the SSO server, including a newly created one with no role or permission, can call admin console APIs. Through these APIs it can read and modify users (including password hashes), reset passwords, manage roles, permissions and organizations, and assign itself the administrator role.Source: github.com
Which versions are affected by CVE-2026-121543?
smart-sso: through 2.0.1.Source: cve.now feed data
Am I affected, and how do I check?
smart-sso through version 2.0.1 is affected, confirmed at project version 2.0.1. The issue applies in the default dev Spring profile, the out-of-the-box configuration in the README, where paths under /admin/** are not configured on the permission management page. To check, look at the project version in the build and whether /admin/** paths are configured on the permission management page.Source: github.com
How do I fix CVE-2026-121543?
Upgrade smart-sso to 2.0.2, which fixes this issue.Source: github.com