dbcve.org
Inverter FirmwareOperating system · Deyeinverter

CVE-2023-0808

MEDIUM · 6.8 CVSS v3.1 Published 2023-02-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
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
A vulnerability was found in Deye/Revolt/Bosswerk Inverter MW3_15U_5406_1.47/MW3_15U_5406_1.471. It has been rated as problematic. This issue affects some unknown processing of the component Access Point Setting Handler. The manipulation with the input 12345678 leads to use of hard-coded password. It is possible to launch the attack on the physical device. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used. Upgrading to version MW3_16U_5406_1.53 is able to address this issue. It is recommended to upgrade the affected component. The identifier VDB-220769 was assigned to this vulnerability.

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

A hardcoded password vulnerability exists in the Access Point Setting Handler of Deye/Revolt/Bosswerk inverters (firmware versions MW3_15U_5406_1.47/1.471). The password '12345678' is hardcoded into the component, allowing authentication bypass when an attacker gains physical access to the device.

MitigationUpgrade the inverter firmware to version MW3_16U_5406_1.53 or later, which replaces the hardcoded password with proper authentication mechanisms.

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
Inverter FirmwareOperating system
Affected:= mw3_15u_5406_1.47= mw3_15u_5406_1.471
Inverter FirmwareOperating system
Affected:= mw3_15u_5406_1.47= mw3_15u_5406_1.471
Inverter FirmwareOperating system
Affected:= mw3_15u_5406_1.47= mw3_15u_5406_1.471

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
Physical
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:P/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 inverter firmware version
    Access the inverter admin interface or check system information page to determine the installed firmware version number
    Affected if The firmware version is MW3_15U_5406_1.47 or MW3_15U_5406_1.471
  2. Confirm device manufacturer
    Verify that the inverter is from Deyeinverter, Revolt Power, or Bosswerk brand
    Affected if The device is one of these three manufacturers and matches the version condition
  3. Locate Access Point settings
    Navigate to the wireless or network settings section of the inverter web interface where Access Point configuration is managed
    Affected if Access Point mode is available and configurable on the device
  4. Verify hardcoded credential presence
    Inspect the Access Point Setting Handler component or configuration files for the presence of hardcoded password '12345678'
    Affected if The hardcoded password '12345678' is found in the Access Point configuration

The environment is affected if the inverter runs firmware version MW3_15U_5406_1.47 or 1.471 from Deye/Revolt/Bosswerk and has the Access Point feature enabled with the hardcoded password present.

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

Upgrade the inverter firmware to version MW3_16U_5406_1.53 or later, which replaces the hardcoded password with proper authentication mechanisms.

Recommended fix High confidence

MW3_16U_5406_1.53

  1. 1. Obtain the firmware update MW3_16U_5406_1.53 from the official Deye/Revolt/Bosswerk manufacturer website or support portal
  2. 2. Review the firmware upgrade instructions provided by the manufacturer
  3. 3. Ensure the inverter is powered on and connected properly before initiating the update
  4. 4. Upload and install the MW3_16U_5406_1.53 firmware using the manufacturer's recommended procedure
  5. 5. After upgrade, verify the Access Point settings no longer accept the hard-coded password '12345678'
  6. 6. Confirm the device operates normally with the new firmware version

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

Fix this in Inverter Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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