{"answers":{"affected":"2 open source packages ship an affected version, including com.shopizer:shopizer.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-36767 exists.","fix":"No fix has been published for CVE-2026-36767 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-36767 is a critical path traversal vulnerability in n/a, published on 30 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-36767 and fix it if it is affected.\n\nWhat it is: CVE-2026-36767 is a critical path traversal vulnerability in n/a, published on 30 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-36767 exists.\n\nAffected packages and fixed versions:\n- com.shopizer:shopizer (Maven): affected all versions up to 2.16.0; no fix listed\n- com.shopizer:shopizer (Maven): affected all versions up to 2.16.0; no fix listed\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-36767/ (Markdown: https://insights.sbomify.com/CVE-2026-36767/index.md)","id":"CVE-2026-36767","markdown":"https://insights.sbomify.com/CVE-2026-36767/index.md","name":"CVE-2026-36767","record":{"aliases":["GHSA-f5w4-7ccj-5m75"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Shopizer e-commerce","requires_auth":"none","summary":"Attackers can write arbitrary files to any writable path via a crafted POST request to the image upload endpoint, potentially leading to code execution.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":10,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"A path traversal vulnerability in the /content/images/add endpoint of shopizer v3.2.5 allows attackers write arbitrary files to any writeable path via a crafted POST request.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Shopizer has a path traversal issue","id":"CVE-2026-36767","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2026-36770"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["2.16.0"],"package":"com.shopizer:shopizer","purl":null,"source":"GHSA-f5w4-7ccj-5m75"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["2.16.0"],"package":"com.shopizer:shopizer","purl":"pkg:maven/com.shopizer/shopizer","source":"GHSA-f5w4-7ccj-5m75"}],"prev":{"headline":"Shopizer is vulnerable to Cross-site Scripting","id":"CVE-2026-36766"},"products":["n/a"],"published":"2026-04-30","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":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-30","vendors":["n/a"]},"summary":"Attackers can write arbitrary files to any writable path via a crafted POST request to the image upload endpoint, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2026-36767/"}