/

CVE-2026-121543

Severity:

HIGH RISK

(8.8)

Incorrect Authorization (CWE-863) in smart-sso Admin APIs

CVE-2026-121543

Deferred

Vulnerability type

Category:

Incorrect Authorization

CWE:

CWE-863

Impact:

Privilege Escalation and Unauthorized Administrative Access

Severity:

HIGH RISK

(8.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

smart-sso's PermissionFilter permits unlisted paths by default, which can allow any authenticated user to access admin console APIs. A user who can reach these endpoints may be able to grant themselves administrator privileges and perform sensitive account or application-management actions.

smart-sso's PermissionFilter permits unlisted paths by default, which can allow any authenticated user to access admin console APIs. A user who can reach these endpoints may be able to grant themselves administrator privileges and perform sensitive account or application-management actions.

Affected context

The issue is described in smart-sso through version 2.0.1 and concerns authorization decisions made by PermissionFilter. It becomes risky when admin API paths are not explicitly listed and the filter treats unlisted paths as permitted, allowing authenticated users to reach operations intended for administrators.

The issue is described in smart-sso through version 2.0.1 and concerns authorization decisions made by PermissionFilter. It becomes risky when admin API paths are not explicitly listed and the filter treats unlisted paths as permitted, allowing authenticated users to reach operations intended for administrators.

Exploit preconditions

  • Attack surface: Admin console APIs handled by PermissionFilter
  • Required access: An authenticated account; the description does not specify a particular role
  • Trigger point: A request to an admin API path that is unlisted in the permission rules, including /admin/user-role/save
  • Why exploitation is possible: Unlisted paths are permitted by default rather than denied unless explicitly authorized
  • Attack surface: Admin console APIs handled by PermissionFilter
  • Required access: An authenticated account; the description does not specify a particular role
  • Trigger point: A request to an admin API path that is unlisted in the permission rules, including /admin/user-role/save
  • Why exploitation is possible: Unlisted paths are permitted by default rather than denied unless explicitly authorized

Why this happens

PermissionFilter uses a permissive default for paths without a matching authorization rule. This is an incorrect authorization pattern: access is granted without verifying that the authenticated user has the required privileges. It maps to CWE-863: Incorrect Authorization.

PermissionFilter uses a permissive default for paths without a matching authorization rule. This is an incorrect authorization pattern: access is granted without verifying that the authenticated user has the required privileges. It maps to CWE-863: Incorrect Authorization.

Potential impact

  • An authenticated user could assign themselves an administrator role
  • An attacker may be able to reset passwords or manage users and roles
  • Applications and integrations could be modified without proper authorization
  • Administrative access could affect connected systems, depending on deployment and integration permissions
  • An authenticated user could assign themselves an administrator role
  • An attacker may be able to reset passwords or manage users and roles
  • Applications and integrations could be modified without proper authorization
  • Administrative access could affect connected systems, depending on deployment and integration permissions

General mitigation guidance

Defensive patterns include:

  • Denying access by default when a path or action has no explicit authorization rule
  • Applying role- and action-based checks consistently at sensitive API endpoints
  • Separating administrative operations from general authenticated-user access
  • Minimizing the privileges granted to service accounts and integrated systems
  • Treating authorization rules as security-critical configuration and validating them before use

Defensive patterns include:

  • Denying access by default when a path or action has no explicit authorization rule
  • Applying role- and action-based checks consistently at sensitive API endpoints
  • Separating administrative operations from general authenticated-user access
  • Minimizing the privileges granted to service accounts and integrated systems
  • Treating authorization rules as security-critical configuration and validating them before use

How teams detect issues like this

Review authorization middleware and endpoint policies for permissive fallbacks, including rules that allow unmatched paths. Code review and static analysis can look for admin handlers without explicit role or permission checks. Runtime policy tests should verify that ordinary authenticated accounts are denied access to role assignment, password management, and other administrative operations; policy enforcement can also require explicit authorization for every sensitive route.

Review authorization middleware and endpoint policies for permissive fallbacks, including rules that allow unmatched paths. Code review and static analysis can look for admin handlers without explicit role or permission checks. Runtime policy tests should verify that ordinary authenticated accounts are denied access to role assignment, password management, and other administrative operations; policy enforcement can also require explicit authorization for every sensitive route.

Sources

SourceLink
github.comgithub.com/a466350665/smart-sso
github.comgithub.com/a466350665/smart-sso/blob/91d2dfef8973d308fa1b762e4c86dfbcbe9793ff/smart-sso-server/src/main/java/openjoe/smart/sso/server/controller/admin/UserRoleController.java
github.comgithub.com/a466350665/smart-sso/blob/91d2dfef8973d308fa1b762e4c86dfbcbe9793ff/smart-sso-starter/smart-sso-starter-client/src/main/java/openjoe/smart/sso/client/filter/PermissionFilter.java#L38-L47
github.comgithub.com/a466350665/smart-sso/commit/9bccabaa5ec5
github.comgithub.com/a466350665/smart-sso/commit/a74a791bea7fc7b06ce95f52ce5805d8d7886d48
github.comgithub.com/a466350665/smart-sso/issues/79
vulncheck.comvulncheck.com/advisories/smart-sso-through-2.0.1-incorrect-authorization-in-permissionfilter-enables-admin-escalation

Frequently asked

questions

The described condition affects authenticated users who can reach the relevant admin APIs. The exact scope may depend on deployment access controls and endpoint exposure.

The description says any authenticated user may call the affected APIs, so administrator privileges are not stated as a prerequisite.

Deny access by default and explicitly authorize each sensitive endpoint based on the user's role or permissions.

Test authorization for both allowed and denied users, review unmatched-route behavior, and require explicit policy coverage for administrative actions.

The described condition affects authenticated users who can reach the relevant admin APIs. The exact scope may depend on deployment access controls and endpoint exposure.

The description says any authenticated user may call the affected APIs, so administrator privileges are not stated as a prerequisite.

Deny access by default and explicitly authorize each sensitive endpoint based on the user's role or permissions.

Test authorization for both allowed and denied users, review unmatched-route behavior, and require explicit policy coverage for administrative actions.

Find out what's already
exploitable in your codebase.