| Title | zsadmin ZS-Admin <=1.0.0 Authorization Bypass |
|---|
| Description | ZS-Admin uses the MyBatis-Plus tenant plugin for field-level multi-tenant isolation. The tenant context should be derived from a trusted server-side authentication context, such as the authenticated user's tenantId. However, the current implementation reads the tenant ID directly from the client-controlled X-Tenant-Id request header and stores it in TenantContext.
MultiTenantHandler later reads this value from TenantContext and injects it into SQL tenant conditions. The application does not compare the supplied tenant ID with the tenant ID stored in the authenticated user's LoginUserInfo. Therefore, a user from tenant 1 can change the request header to tenant 2, causing the generated SQL condition to become tenant_id = 2. |
|---|
| Source | ⚠️ https://github.com/zsadmin2025/zs-admin-java/issues/5 |
|---|
| User | cl0ney (UID 99026) |
|---|
| Submission | 06/15/2026 17:48 (2 months ago) |
|---|
| Moderation | 07/21/2026 10:55 (1 month later) |
|---|
| Status | Accepted |
|---|
| VulDB entry | 380829 [zsadmin2025 ZS-Admin up to b52e14536d59fda11e56e2536a1c32e82a38cead MyBatis-Plus Tenant Plugin page getTenantId X-Tenant-Id authorization] |
|---|
| Points | 20 |
|---|