Executive brief
JeecgBoot, a low-code development platform, contains a security flaw in its OpenAPI management module. An attacker with a standard user account can view, modify, or delete sensitive API credentials (Access Keys and Secret Keys) belonging to any user, including administrators. This allows the attacker to impersonate high-privileged users and perform unauthorized actions across the system's API, potentially leading to full data theft or system takeover.
Technical details
JeecgBoot through 3.9.2 suffers from missing authorization checks in the OpenApiAuthController and OpenApiPermissionController components. These endpoints lack Shiro authorization annotations, allowing any authenticated user to perform create, read, update, and delete (CRUD) operations on OpenAPI Access Key/Secret Key (AK/SK) pairs. Furthermore, the /openapi/call/{path} handler fails to verify the SK-signed signature, relying solely on the AK provided in the request header. By combining these flaws, a low-privileged attacker can retrieve plaintext credentials for administrative accounts and invoke proxy API routes with the permissions of the credential owner, leading to full administrative impersonation.
Affected products
- JeecgBoot JeecgBoot through 3.9.2
Timeline
- 2026-06-14: disclosed: Issue reported on GitHub repository
- 2026-06-30: advisory: NVD and VulnCheck published advisory