dbcve.org
Sustainable Irrigation PlatformApplication · Dan In Ca

CVE-2026-58476

HIGH · 8.1 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to after 5.2.16 or later.
See remediation →
88/100
Remediation priority · High
Remotely reachable No privileges 5 weeks old

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 · unedited
Sustainable Irrigation Platform (SIP) through version 5.2.16 contains a cross-site request forgery vulnerability that allows remote attackers to perform state-changing administrative actions by luring a logged-in administrator into visiting a malicious page that issues HTTP GET requests without CSRF token validation or origin verification. Attackers can trigger actions such as disabling the passphrase, rebooting the device, deleting programs, or installing plugins, with the default configuration exposing these endpoints to unauthenticated users due to no required passphrase and a default credential of 'opendoor'.

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 · high confidence

The Sustainable Irrigation Platform (SIP) versions up to 5.2.16 lacks CSRF protection on state-changing administrative endpoints. Remote attackers can craft malicious web pages that, when visited by a logged-in administrator, automatically trigger HTTP GET requests to perform privileged actions including disabling the passphrase, rebooting the device, deleting programs, and installing plugins. The default configuration compounds this by exposing these endpoints without authentication due to a missing passphrase requirement and the default credential 'opendoor'.

MitigationImplement CSRF token validation and origin/referer verification on all state-changing endpoints, enforce passphrase requirements in the default configuration, and change the default credential from '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
Sustainable Irrigation PlatformApplication
Affected:<= 5.2.16

CVSS 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
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify SIP installation and version
    Locate the Dan In Ca Sustainable Irrigation Platform installation and determine the installed version number. Compare your version against the affected range: versions 5.2.16 and prior.
    Affected if The installed version is 5.2.16 or lower.
  2. Check for default credential usage
    Inspect the authentication configuration to determine if the default credential 'opendoor' is still in use for administrative access.
    Affected if The default credential 'opendoor' has not been changed.
  3. Verify admin endpoint exposure
    Test whether administrative endpoints (used for passphrase, reboot, program deletion, and plugin installation actions) are accessible without authentication in the default configuration.
    Affected if Admin endpoints are accessible without requiring authentication in the default configuration.
  4. Inspect CSRF protection on state-changing endpoints
    Examine the HTTP requests and responses for state-changing admin actions (disable passphrase, reboot, delete programs, install plugins) to determine if CSRF tokens are validated and Origin/referer headers are verified.
    Affected if State-changing endpoints lack CSRF token validation and Origin/referer header verification.

You are affected if your SIP version is 5.2.16 or lower and admin endpoints lack CSRF protection or are exposed without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 5.2.16
Interim mitigation

Implement CSRF token validation and origin/referer verification on all state-changing endpoints, enforce passphrase requirements in the default configuration, and change the default credential from 'opendoor'.

Fix this in Sustainable Irrigation Platform Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-58476 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-58476 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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