{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42176 exists.","fix":"No fix has been published for CVE-2026-42176 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-42176 is a medium-severity authentication bypass vulnerability in Erudika scoold, published on 8 May 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-42176 and fix it if it is affected.\n\nWhat it is: CVE-2026-42176 is a medium-severity authentication bypass vulnerability in Erudika scoold, published on 8 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42176 exists.\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-42176/ (Markdown: https://insights.sbomify.com/CVE-2026-42176/index.md)","id":"CVE-2026-42176","markdown":"https://insights.sbomify.com/CVE-2026-42176/index.md","name":"CVE-2026-42176","record":{"aliases":["GHSA-7qfx-c234-xg4g"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["privilege_escalation","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Scoold Q\u0026A platform","requires_auth":"high_privilege","summary":"Attackers can forge JWTs to modify admin settings, gaining persistent administrator access after a service restart.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.7,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"Scoold is a Q\u0026A and a knowledge sharing platform for teams. Prior to version 1.67.0, Scoold allows the admins configuration value to be modified through /api/config/set/admins with a forged Bearer token that is accepted as an admin API token. Once that setting is changed, the target email address is written to the application configuration file. The change does not become active immediately in the current process, because the ADMINS set is loaded once at startup. After a Scoold restart, though, the selected user is recognized as an administrator and gains access to the admin panel. This issue gives an attacker a reliable persistence path: write their own email into scoold.admins, wait for a restart or trigger one operationally, and the account comes back as admin. This issue has been patched in version 1.67.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Auth bypass in scoold","id":"CVE-2026-42176","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"linux-entra-sso: PRT SSO cookie can leak to attacker-controlled hosts when broad host permissions are granted","id":"CVE-2026-42177"},"packages":[],"prev":{"headline":"requests-hardened: Server-Side Request Forgery (SSRF) in requests-hardened RFC 6598","id":"CVE-2026-42175"},"products":["scoold"],"published":"2026-05-08","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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-05-08","vendors":["Erudika"]},"summary":"Attackers can forge JWTs to modify admin settings, gaining persistent administrator access after a service restart.","url":"https://insights.sbomify.com/CVE-2026-42176/"}