{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-54676 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-54676 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-54676 is a medium-severity missing authorization vulnerability in Erudika scoold, published on 17 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-54676 and fix it if it is affected.\n\nWhat it is: CVE-2026-54676 is a medium-severity missing authorization vulnerability in Erudika scoold, published on 17 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-54676 in the wild and no public exploit code.\n\nAffected product: Erudika scoold. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-54676/ (Markdown: https://insights.sbomify.com/CVE-2026-54676/index.md)","id":"CVE-2026-54676","markdown":"https://insights.sbomify.com/CVE-2026-54676/index.md","name":"CVE-2026-54676","record":{"aliases":["GHSA-2cff-ppf7-pc42"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Q\u0026A knowledge platform","requires_auth":"low_privilege","summary":"Attackers with personal API tokens can read private replies in inaccessible spaces due to missing authorization checks in the answers endpoint.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"Scoold is a Q\u0026A and a knowledge sharing platform for teams. Prior to 1.69.0, users with personal API tokens can retrieve replies from questions in private spaces they cannot access because src/main/java/com/erudika/scoold/api/ApiController.java in ApiController.getPostReplies() does not apply canAccessSpace before returning data from GET /api/posts/{id}/answers. The issue is reachable when scoold.api_user_access_enabled and scoold.api_enabled are true and a token holder knows or enumerates a private question identifier. Under those conditions, the question endpoint can deny access while the answers endpoint returns the private reply bodies, exposing confidential team or project discussions. This issue is fixed in version 1.69.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Scoold: GET /api/posts/{id}/answers leaks private-space replies when personal API tokens are enabled","id":"CVE-2026-54676","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Scoold: Authenticated user can post replies and comments to private-space questions without space membership","id":"CVE-2026-54677"},"packages":[],"prev":{"headline":"FreePBX: Authenticated Remote Code Execution via File Upload and Convert in Soundlang Module","id":"CVE-2026-54675"},"products":["scoold"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-18","vendors":["Erudika"]},"summary":"Attackers with personal API tokens can read private replies in inaccessible spaces due to missing authorization checks in the answers endpoint.","url":"https://insights.sbomify.com/CVE-2026-54676/"}