{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-60114 exists.","fix":"No fix has been published for CVE-2026-60114 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-60114 is a high-severity path traversal vulnerability in Dan-in-CA SIP, published on 14 Jul 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-60114 and fix it if it is affected.\n\nWhat it is: CVE-2026-60114 is a high-severity path traversal vulnerability in Dan-in-CA SIP, published on 14 Jul 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-60114 exists.\n\nAffected product: Dan-in-CA SIP. 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-60114/ (Markdown: https://insights.sbomify.com/CVE-2026-60114/index.md)","id":"CVE-2026-60114","markdown":"https://insights.sbomify.com/CVE-2026-60114/index.md","name":"CVE-2026-60114","record":{"aliases":["AZL-92370","GHSA-9xpx-72mq-c8x9"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Irrigation platform","requires_auth":"none","summary":"Attackers can write arbitrary files via path traversal in JSON backup restore, potentially leading to code execution or data modification.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"sustainable_irrigation_platform","vendor":"dan-in-ca"}],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Sustainable Irrigation Platform (SIP) through version 5.2.16 contains a path traversal vulnerability that allows attackers with access to the restore functionality to write files to arbitrary locations by uploading crafted JSON backup files with unvalidated keys used to construct file paths. Attackers can exploit the lack of key validation in the JSON restore process, combined with the absence of a required passphrase in the default configuration or the default passphrase 'opendoor', to write arbitrary JSON files outside the intended data directory.","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":"Sustainable Irrigation Platform 5.2.16 Path Traversal via JSON Backup Restore","id":"CVE-2026-60114","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2026-60115"},"packages":[],"prev":{"headline":"AIT-DSN \u003c 2.2.2 Missing Authentication via SLE API Routes","id":"CVE-2026-60113"},"products":["SIP"],"published":"2026-07-14","related":[{"cvss_score":9.2,"headline":"Sustainable Irrigation Platform 5.2.16 RCE via cli_control Plugin Command Injection","id":"CVE-2026-58479","kev_date_added":null,"published":"2026-07-14"},{"cvss_score":8.8,"headline":"Sustainable Irrigation Platform 5.2.16 Mass Assignment via HTTP Parameters","id":"CVE-2026-58477","kev_date_added":null,"published":"2026-07-14"},{"cvss_score":7,"headline":"Sustainable Irrigation Platform 5.2.16 CSRF via Administrative GET Requests","id":"CVE-2026-58476","kev_date_added":null,"published":"2026-07-14"},{"cvss_score":6.3,"headline":"Sustainable Irrigation Platform 5.2.16 SSRF via Node-RED Callback URL","id":"CVE-2026-58478","kev_date_added":null,"published":"2026-07-14"},{"cvss_score":5.3,"headline":"Sustainable Irrigation Platform 5.2.16 Stored XSS via Program Name","id":"CVE-2026-58475","kev_date_added":null,"published":"2026-07-14"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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":"partial"},"state":"PUBLISHED","updated":"2026-07-14","vendors":["Dan-in-CA"]},"summary":"Attackers can write arbitrary files via path traversal in JSON backup restore, potentially leading to code execution or data modification.","url":"https://insights.sbomify.com/CVE-2026-60114/"}