/

CVE-2026-58377

Severity:

HIGH RISK

(8.1)

Broken Access Control (CWE-862) in JeecgBoot OpenAPI

CVE-2026-58377

Deferred

Vulnerability type

Category:

Broken Access Control

CWE:

CWE-862

Impact:

Credential Theft and Unauthorized API Access

Severity:

HIGH RISK

(8.1)

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

JeecgBoot through 3.9.2 suffers from broken access control on OpenAPI credential management endpoints, allowing low-privilege authenticated users to perform unrestricted CRUD operations on AK/SK pairs.

Because secret keys are returned in plaintext, attackers can steal credentials and invoke the full OpenAPI surface without proper authorization.

Affected context

The vulnerability arises in JeecgBoot deployments that expose the OpenApiAuthController and OpenApiPermissionController endpoints for managing OpenAPI access keys and secret keys.

In affected setups, these endpoints are reachable to authenticated users without fine-grained Shiro authorization checks or role-based restrictions, and responses may include plaintext secret keys.

Exploit preconditions

  • Attack surface: HTTP endpoints of JeecgBoot's OpenAPI management controllers.
  • Required access: Valid but low-privilege authenticated account within the JeecgBoot application.
  • Trigger point: Direct invocation of OpenApiAuthController and OpenApiPermissionController methods that lack Shiro authorization annotations.
  • Why exploitation is possible: Missing or incomplete server-side authorization allows any authenticated user to list, create, modify, and delete credentials, including viewing secret keys in plaintext.

Why this happens

This issue stems from insufficient server-side authorization checks on sensitive controller endpoints responsible for managing OpenAPI credentials.

The OpenApiAuthController and OpenApiPermissionController lack Shiro authorization annotations or equivalent access-control enforcement, meaning the application relies solely on authentication without validating whether the caller is permitted to manage credentials.

Conceptually, this maps to CWE-862: Missing Authorization, where privileged operations are exposed without robust, centralized permission checks, allowing overbroad access for low-privilege users.

Potential impact

  • Attackers may list all OpenAPI AK/SK credential pairs and obtain secret keys in plaintext.
  • Low-privilege users could create new credential sets for persistent unauthorized API usage.
  • Existing credentials can be edited or deleted, disrupting legitimate integrations and services.
  • Unauthorized invocation of OpenAPI endpoints may lead to data exposure, manipulation, or service abuse.
  • Credential compromise can enable lateral movement into connected systems that trust JeecgBoot's API calls.

General mitigation guidance

Mitigation focuses on enforcing strict, centralized authorization for all sensitive operations around credential management and API access.

Recommended design patterns include:

  • Applying role-based access control (RBAC) or policy-based access control to all controllers that handle AK/SK creation, listing, and deletion.
  • Ensuring that authorization checks are performed server-side using a consistent framework (e.g., Shiro, Spring Security) rather than relying on client-side enforcement.
  • Limiting credential visibility so that secret keys are never returned in plaintext after initial creation, and masking or omitting sensitive fields in API responses.
  • Segmenting administrative functions into dedicated endpoints restricted to tightly controlled roles.
  • Designing APIs with least-privilege principles, granting only the minimal operations required for each user or integration.

How teams detect issues like this

Detection typically involves reviewing both code and runtime behavior for missing or weak authorization around sensitive endpoints.

Useful strategies include:

  • Static analysis rules that flag controller methods lacking authorization annotations or security interceptors, especially in credential or permission-related modules.
  • Manual code review focused on API controllers, verifying that every operation modifying credentials or permissions passes through centralized access-control logic.
  • Logging and monitoring of access to OpenAPI management endpoints, with alerts on unexpected usage patterns by low-privilege accounts.
  • Security tests or penetration testing scenarios that attempt credential management actions with non-administrative roles to confirm enforcement of RBAC policies.

Sources

SourceLink
github.comgithub.com/jeecgboot/JeecgBoot/issues/9705
vulncheck.comvulncheck.com/advisories/jeecgboot-missing-authorization-on-openapi-credential-management-endpoints-exposes-access-secret-keys

Frequently asked

questions

Any authenticated user with network access to the JeecgBoot application can attempt to call the exposed OpenAPI management endpoints. Without proper authorization checks, these users can fully manage AK/SK credentials and access the OpenAPI surface.

The attacker needs only a low-privilege, authenticated account. Administrative privileges are not required if authorization enforcement is missing from the affected controllers.

The safest approach is to enforce strict server-side authorization on all credential management and permission-related endpoints, restricting them to dedicated administrative roles and preventing plaintext exposure of secret keys in responses.

Apply a standardized access-control framework across all controllers, require authorization annotations or policies for every sensitive operation, implement least-privilege RBAC, and include security-focused code review and automated checks in the development lifecycle to catch missing authorization early.

Find out what's already
exploitable in your codebase.