dbcve.org
Sustainable Irrigation PlatformApplication · Dan In Ca

CVE-2026-58479

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to after 5.2.16 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 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 command injection vulnerability in the optional cli_control plugin that allows unauthenticated or cross-site request forgery attackers to execute arbitrary operating-system commands by storing a malicious payload via the plugin's HTTP endpoint. Attackers can trigger execution by activating the associated irrigation station, exploiting the absence of passphrase protection or the default passphrase 'opendoor', to achieve arbitrary command execution on the underlying host.

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 confidence

The Sustainable Irrigation Platform (SIP) versions up to 5.2.16 contain a command injection vulnerability in the optional cli_control plugin. Attackers can send malicious operating-system commands via the plugin's HTTP endpoint by storing a malicious payload, then trigger execution by activating the associated irrigation station. The vulnerability is exploitable by unauthenticated attackers or via CSRF, due to the absence of passphrase protection or use of the default passphrase 'opendoor'.

MitigationUpgrade to a version beyond 5.2.16 if available, change the default passphrase 'opendoor' to a strong unique passphrase, and disable the cli_control plugin if not needed.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 Sustainable Irrigation Platform installation and determine its installed version number. Common locations include /opt/sip, /usr/local/sip, or the application's web root directory. Check version files, about pages, or the application's startup output.
    Affected if The installed version is 5.2.16 or any earlier version (anything <= 5.2.16).
  2. Verify cli_control plugin status
    Examine the SIP configuration to determine whether the cli_control plugin is installed and enabled. Look for plugin configuration files, the plugins directory, or the main configuration file's plugin list.
    Affected if The cli_control plugin is enabled or loaded in the configuration.
  3. Inspect cli_control plugin configuration
    Open the cli_control plugin configuration file. Look for settings related to passphrase protection, authentication, or access control. Check whether a passphrase is required for plugin operations.
    Affected if No passphrase is configured, or passphrase protection is disabled.
  4. Check for default passphrase usage
    Locate the passphrase setting within the cli_control plugin configuration or the main SIP configuration file. Examine the value to determine if it matches the default passphrase 'opendoor'.
    Affected if The configured passphrase is 'opendoor' or remains at its default unset state.

A user is affected if running SIP version 5.2.16 or earlier WITH the cli_control plugin enabled AND either no passphrase is set or the default passphrase 'opendoor' is in use.

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

Upgrade to a version beyond 5.2.16 if available, change the default passphrase 'opendoor' to a strong unique passphrase, and disable the cli_control plugin if not needed.

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-58479 — 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-58479 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