dbcve.org
Envoy FirmwareOperating system · Enphase

CVE-2023-33869

CRITICAL · 9.8 CVSS v3.1 Published 2023-06-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Enphase Envoy versions D7.0.88 is vulnerable to a command injection exploit that may allow an attacker to execute root commands.

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

Enphase Envoy D7.0.88 contains a command injection vulnerability that allows unauthenticated attackers to inject and execute arbitrary operating system commands with root privileges. This critical flaw likely stems from improper input validation in web interface parameters that are passed to system shell calls.

MitigationApply vendor-supplied firmware patch or upgrade to a patched version; if no patch exists, restrict network access to the Envoy management interface and monitor for indicators of compromise.

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
Envoy FirmwareOperating system
Affected:= d7.0.88

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 Enphase Envoy device
    Locate Enphase Envoy hardware on your network or physical premises. This is a solar panel monitoring and communication device typically installed near solar inverters or electrical panels.
    Affected if An Enphase Envoy device is present in your environment
  2. Check firmware version
    Access the Envoy web interface (typically at its IP address) and navigate to Administration > Software, or check the device label/display. Alternatively, use the Enphase API or mobile app to query the firmware version.
    Affected if The installed firmware version is exactly d7.0.88
  3. Verify web interface accessibility
    Confirm the Envoy web management interface is reachable on the network (HTTP/HTTPS on ports 80/443 or custom management ports).
    Affected if The web interface is network-accessible (this is required for the unauthenticated attack vector)
  4. Check for indicators of compromise
    Review system logs for unexpected shell command executions, unusual processes running as root, or unexpected outbound network connections from the Envoy device.
    Affected if Evidence exists of unauthorized command execution or unexpected system behavior

You are affected if you have an Enphase Envoy device running exactly firmware version d7.0.88 with an accessible web management interface.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied firmware patch or upgrade to a patched version; if no patch exists, restrict network access to the Envoy management interface and monitor for indicators of compromise.

Recommended fix Moderate confidence

Latest available Envoy firmware version (contact Enphase support or check Enphase documentation for the specific fixed release)

  1. 1. Check the Enphase official support website or contact Enphase support for the latest available firmware version that addresses CVE-2023-33869.
  2. 2. Before upgrading, backup any existing configuration if the firmware supports configuration export.
  3. 3. Download the latest stable Envoy firmware version from Enphase's official source.
  4. 4. Follow Enphase's standard firmware upgrade procedure for the Envoy device, typically via the local web interface or Enphase Installer app.
  5. 5. After upgrade, verify the device is functioning normally and the vulnerable firmware version (D7.0.88) is no longer installed.
Caveat Review Enphase release notes for any configuration or compatibility changes between D7.0.88 and the target firmware version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Envoy Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-33869 — 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-2023-33869 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