CVE-2026-60114
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSustainable 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceSustainable Irrigation Platform (SIP) versions up to 5.2.16 contain a path traversal vulnerability in the JSON restore functionality. Attackers with access to the restore feature can craft malicious JSON backup files where keys contain path traversal sequences (e.g., '../') to write arbitrary files outside the intended data directory. The vulnerability is exacerbated by either a missing passphrase requirement in default configuration or use of the default passphrase 'opendoor'.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 5.2.16CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed versionLocate and inspect the version information for the Dan In Ca Sustainable Irrigation Platform installation (check application metadata, about page, or version file)Affected if The installed version is 5.2.16 or any version lower than 5.2.16 (e.g., 5.2.15, 5.2.10, etc.)
-
Verify JSON restore feature statusInspect the application's enabled features, modules, or administrative settings to determine whether the JSON restore functionality is currently active and accessibleAffected if The JSON restore feature is enabled and accessible to the attacker (regardless of authentication level)
-
Examine passphrase configurationLocate and review the backup/restore security settings - check whether passphrase protection is mandatory and inspect the configured passphrase value if one is setAffected if Passphrase protection is not enforced as mandatory OR the configured passphrase matches the default value 'opendoor'
-
Audit file write locationsReview application logs, recently created or modified files, and the data directory structure to identify any files written outside the intended data directoryAffected if Any unexpected files appear outside the designated data directory, particularly in system directories or application root
You are affected if your installation is version 5.2.16 or lower AND the JSON restore feature is accessible AND either passphrase protection is not enforced or the default passphrase 'opendoor' is in use.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict input validation on JSON keys to reject path traversal sequences, enforce mandatory passphrase protection with secure defaults, and restrict all file write operations to the designated data directory using canonical path resolution.
- Consultation2.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-60114 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-60114 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data