dbcve.org
Hard-coded CredentialsWeakness · CWE-798

CVE-2025-5023

HIGH · 7.1 CVSS v3.1 Published 2025-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
76/100
Remediation priority · High
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
Use of Hard-coded Credentials vulnerability in Mitsubishi Electric Corporation photovoltaic system monitor “EcoGuideTAB” PV-DR004J all versions and PV-DR004JA all versions allows an attacker within the Wi-Fi communication range between the units of the product (measurement unit and display unit) to disclose information such as generated power and electricity sold back to the grid stored in the product, tamper with or destroy stored or configured information in the product, or cause a Denial-of-Service (DoS) condition on the product, by using hardcoded user ID and password common to the product series obtained by exploiting CVE-2025-5022. The affected products discontinued in 2015, support ended in 2020.

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

Hardcoded credentials vulnerability in Mitsubishi Electric EcoGuideTAB PV-DR004J/JA photovoltaic monitoring system allows an attacker within Wi-Fi communication range between the measurement and display units to read generated power/electricity data, modify or delete stored configuration, or cause denial of service by using a hardcoded user ID and password common to the product series.

MitigationSince the affected products were discontinued in 2015 and support ended in 2020 with no firmware updates available, organizations should isolate these devices on restricted network segments, implement monitoring for anomalous Wi-Fi activity, or replace with supported hardware.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/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 the device model
    Locate the product label or check system information for the model number PV-DR004J or PV-DR004JA
    Affected if The device is confirmed to be a Mitsubishi Electric EcoGuideTAB PV-DR004J/JA unit
  2. Check if Wi-Fi communication is enabled
    Verify whether the measurement and display units are communicating via Wi-Fi. Consult the device documentation or check Wi-Fi status indicators on the unit.
    Affected if Wi-Fi communication between measurement and display units is active, as the vulnerability is exploited via Wi-Fi proximity
  3. Assess network exposure
    Determine whether the device is isolated on a restricted network segment or if it is accessible from broader network infrastructure
    Affected if The device is on an unrestricted or poorly segmented network, allowing potential attackers within Wi-Fi range to access it
  4. Monitor for unauthorized Wi-Fi activity
    Use Wi-Fi monitoring tools to detect unexpected connections or authentication attempts targeting the device SSID
    Affected if Unrecognized devices or repeated authentication attempts are observed on the Wi-Fi network used by the monitoring system

A user is affected if they operate an active PV-DR004J/JA unit with Wi-Fi communication enabled and the device is not isolated from potential unauthorized access within Wi-Fi range.

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

Since the affected products were discontinued in 2015 and support ended in 2020 with no firmware updates available, organizations should isolate these devices on restricted network segments, implement monitoring for anomalous Wi-Fi activity, or replace with supported hardware.

Recommended fix High confidence
  1. This vulnerability affects discontinued products (PV-DR004J and PV-DR004JA) that have been discontinued since 2015 and had support ended in 2020.
  2. Mitsubishi Electric has not released any patches, firmware updates, or fixed versions for these products.
  3. No vendor-provided configuration mitigations are available for hard-coded credentials embedded in firmware.
  4. Consider replacing the affected photovoltaic system monitors with newer, supported products from Mitsubishi Electric or alternative vendors.
  5. If continued use is unavoidable, isolate the affected devices on a separate network segment with strict firewall rules to limit exposure to attackers within Wi-Fi communication range.

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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