CVE-2026-57183
Scoold is a Q&A and a knowledge sharing platform for teams. Prior …
Scoold is a Q&A and a knowledge sharing platform for teams. Prior to 1.69.1, checkApiAuth() in src/main/java/com/erudika/scoold/utils/ScooldUtils.java accepts a JWT signed with app_secret_key or para_secret_key for /api/config and /api/stats without requiring a registered API-key jti, and maps the request to the hardcoded administrative API_USER. The special endpoint checks run even when scoold.api_enabled is false. An attacker who obtains either signing secret can forge a token that reads sensitive configuration and server logs and reaches privileged configuration functionality, while an ordinary login-session token is not sufficient. This issue is fixed in version 1.69.1.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/Erudika/scoold/commit/de018c17a60c352f318109a762a377c325a5fd97
- github.com/Erudika/scoold/commit/e527d4da1ac04b6a35bd86e560c279f0160c5c02
- github.com/Erudika/scoold/releases/tag/1.69.1
- github.com/Erudika/scoold/security/advisories/GHSA-6q9q-cqq5-hvmq
- nvd.nist.gov/vuln/detail/CVE-2026-57183
- cve.org/CVERecord?id=CVE-2026-57183
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.