CVE-2026-93954: grimmory-tools grimmory Settings API Endpoint AppSettingController.java AppSettingController.getAppSettings authorization
A security vulnerability has been detected in grimmory-tools grimmory up to 3.3.3/3.4.1. Affected is the function AppSettingController.getAppSettings of the file backend/src/main/java/org/booklore/controller/AppSettingController.java of the component Settings API Endpoint. Such manipulation leads to incorrect authorization. The attack can be launched remotely. The exploit has been disclosed publicly and may be used. The name of the patch is 2b66ca6df8110f6b512e030b54c16b9fbe318f17. Applying a patch is advised to resolve 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
grimmory-tools grimmory Settings API Endpoint (AppSettingController.getAppSettings)to a version that resolves this vulnerability.Fixed in 3.3.3/3.4.1Patch 2b66ca6df8110f6b512e030b54c16b9fbe318f17
Event History
Frequently Asked Questions
Which deployments are affected?
grimmory-tools grimmory versions up to 3.3.3 and 3.4.1 are affected. The issue is in the Settings API endpoint implemented by AppSettingController.getAppSettings.
What access does an attacker need?
The attack can be launched remotely and requires low privileges. No user interaction is required.
Is public exploitation a concern?
Yes. An exploit has been publicly disclosed and may be used.
What should be done to remediate the issue?
Apply patch 2b66ca6df8110f6b512e030b54c16b9fbe318f17. PR #2558, merged as 53abc8b, moved the OIDC secret into a dedicated setting but did not itself restrict GET /api/v1/settings.