CVE-2026-58377
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedJeecgBoot through 3.9.2 contains a broken access control vulnerability that allows authenticated low-privilege users to perform full create, read, update, and delete operations on OpenAPI credentials by accessing the OpenApiAuthController and OpenApiPermissionController endpoints which lack Shiro authorization annotations. Attackers can exploit the unenforced access controls to list, add, edit, and delete all AK/SK credential pairs, with the list endpoint returning secret keys in plaintext, enabling credential theft and unauthorized invocation of the OpenAPI surface.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceJeecgBoot through 3.9.2 has a broken access control vulnerability in the OpenAPI credential management endpoints (OpenApiAuthController and OpenApiPermissionController). These endpoints lack Shiro authorization annotations, allowing any authenticated user—including low-privilege users—to perform full CRUD operations on OpenAPI AK/SK credential pairs. The list endpoint additionally returns secret keys in plaintext, enabling credential theft and unauthorized API surface invocation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify JeecgBoot versionLocate the version file or build configuration (e.g., pom.xml, application.yml, or the JAR manifest) and confirm the installed version numberAffected if Version is 3.9.2 or earlier
-
Verify OpenApiAuthController existsSearch the application codebase or decompiled classes for the class OpenApiAuthController and confirm its presence in the deployed applicationAffected if The controller class exists in the application
-
Inspect Shiro authorization annotations on OpenApiAuthControllerExamine the source code or decompiled bytecode of OpenApiAuthController methods and check whether @RequiresPermissions or @RequiresRoles annotations are present on CRUD endpoints (create, update, delete, list)Affected if No Shiro authorization annotations are found on the CRUD methods
-
Inspect OpenApiPermissionController for missing annotationsExamine OpenApiPermissionController in the same manner to verify whether authorization annotations are applied to its endpointsAffected if No Shiro authorization annotations are present on the controller methods
-
Test list endpoint for plaintext secret exposureAuthenticate as a low-privilege user and call the OpenAPI credentials list endpoint; inspect the response to determine if secret keys or API keys are returned in plaintextAffected if The response contains plaintext secret keys or API keys without masking
A user is affected if they run JeecgBoot version 3.9.2 or earlier and the OpenApiAuthController/OpenApiPermissionController endpoints lack Shiro authorization annotations, allowing low-privilege users to access plaintext secrets.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataAdd proper Shiro authorization annotations (e.g., @RequiresPermissions, @RequiresRoles) to OpenApiAuthController and OpenApiPermissionController endpoints to enforce role-based access control. Modify the list endpoint to mask or hash secret keys instead of returning plaintext values.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-58377 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-58377 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data