{"answers":{"affected":"2 open source packages ship an affected version, including almirhodzic/nova-toggle-5.","exploited":"There is no known exploitation of CVE-2026-42202 in the wild and no public exploit code.","fix":"Upgrade almirhodzic/nova-toggle-5 to 1.3.0 or later.","what":"CVE-2026-42202 is a medium-severity missing authorization vulnerability in almirhodzic nova-toggle-5, published on 8 May 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-42202 and fix it if it is affected.\n\nWhat it is: CVE-2026-42202 is a medium-severity missing authorization vulnerability in almirhodzic nova-toggle-5, published on 8 May 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-42202 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- almirhodzic/nova-toggle-5 (Packagist): affected all versions; fixed in 1.3.0\n- almirhodzic/nova-toggle-5 (Packagist): affected all versions; fixed in 1.3.0\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-42202/ (Markdown: https://insights.sbomify.com/CVE-2026-42202/index.md)","id":"CVE-2026-42202","markdown":"https://insights.sbomify.com/CVE-2026-42202/index.md","name":"CVE-2026-42202","record":{"aliases":["GHSA-f5c8-m5vw-rmgq"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Laravel Nova plugin","requires_auth":"low_privilege","summary":"Authenticated users without Nova access can modify boolean fields on any resource via the toggle endpoint due to missing authorization checks.","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:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-285","name":"Improper Authorization"}],"description":"nova-toggle-5 enables fliping booleans in the index. Prior to version 1.3.0, the toggle endpoint (POST/nova-vendor/nova-toggle/toggle/{resource}/{resourceId}) was protected only by web + auth:\u003cguard\u003e middleware. Any user authenticated on the configured guard could call the endpoint and flip boolean attributes on any Nova resource — including users who do not have access to Nova itself (for example, frontend customers sharing the web guard with the Nova admin area). The endpoint also accepted an arbitrary attribute parameter, which meant a valid caller could toggle any boolean column on the underlying model — not just columns exposed as Toggle fields on the resource. This issue has been patched in version 1.3.0.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"nova-toggle-5: Improper authorization on toggle endpoint allowed non-Nova users to modify boolean fields","id":"CVE-2026-42202","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"LiteLLM: Server-Side Template Injection in /prompts/test endpoint","id":"CVE-2026-42203"},"packages":[{"ecosystem":"Packagist","fixed":["1.3.0"],"introduced":["0"],"last_affected":[],"package":"almirhodzic/nova-toggle-5","purl":null,"source":"GHSA-f5c8-m5vw-rmgq"},{"ecosystem":"Packagist","fixed":["1.3.0"],"introduced":["0"],"last_affected":[],"package":"almirhodzic/nova-toggle-5","purl":"pkg:composer/almirhodzic/nova-toggle-5","source":"GHSA-f5c8-m5vw-rmgq"}],"prev":{"headline":"Coolify: OS Command Injection via Database Credential Fields in Docker Compose Service Commands","id":"CVE-2026-42201"},"products":["nova-toggle-5"],"published":"2026-05-08","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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-05-11","vendors":["almirhodzic"]},"summary":"Authenticated users without Nova access can modify boolean fields on any resource via the toggle endpoint due to missing authorization checks.","url":"https://insights.sbomify.com/CVE-2026-42202/"}