grimmory-tools grimmory up to 3.3.3/3.4.1 Settings API Endpoint AppSettingController.java AppSettingController.getAppSettings authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.9 | $0-$5k | 1.94- |
Summary
A vulnerability identified as problematic has been detected in grimmory-tools grimmory up to 3.3.3/3.4.1. Affected by this vulnerability is the function AppSettingController.getAppSettings of the file backend/src/main/java/org/booklore/controller/AppSettingController.java of the component Settings API Endpoint. Performing a manipulation results in authorization.
This vulnerability was named CVE-2026-93954. The attack may be initiated remotely. In addition, an exploit is available.
It is suggested to install a patch to address this issue.
PR #2558, merged as 53abc8b, moved the OIDC secret into a dedicated setting, but did not by itself restrict GET /api/v1/settings.
Details
A vulnerability was found in grimmory-tools grimmory up to 3.3.3/3.4.1. It has been classified as problematic. This affects the function AppSettingController.getAppSettings of the file backend/src/main/java/org/booklore/controller/AppSettingController.java of the component Settings API Endpoint. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-863. The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions. This is going to have an impact on confidentiality.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-93954. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details and a public exploit are known.
The exploit is shared for download at github.com. It is declared as proof-of-concept. PR #2558, merged as 53abc8b, moved the OIDC secret into a dedicated setting, but did not by itself restrict GET /api/v1/settings.
Applying the patch 2b66ca6df8110f6b512e030b54c16b9fbe318f17 is able to eliminate this problem. The bugfix is ready for download at github.com.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 3.9
VulDB Base Score: 4.3
VulDB Temp Score: 3.9
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-863 / CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔒
Patch: 2b66ca6df8110f6b512e030b54c16b9fbe318f17
Timeline
09/19/2026 Advisory disclosed09/19/2026 VulDB entry created
09/19/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 2430
Status: Confirmed
Confirmation: 🔒
CVE: CVE-2026-93954 (🔒)
GCVE (CVE): GCVE-0-2026-93954
GCVE (VulDB): GCVE-100-407913
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 09/19/2026 10:56Changes: 09/19/2026 10:56 (62)
Complete: 🔍
Submitter: summmm
Cache ID: 216::103
Submit
Accepted
- Submit #943919: grimmory-tools grimmory 3.3.3 Incorrect Access Control (by summmm)
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.