CVE-2025-36752
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 · uneditedGrowatt ShineLan-X communication dongle has an undocumented backup account with undocumented credentials which allows significant level access to the device, such as allowing any attacker to access the Setting Center. This means that this is effectively backdoor for all devices utilizing a Growatt ShineLan-X communication dongle.
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 confidenceThe Growatt ShineLan-X communication dongle contains a hardcoded backdoor account with undocumented credentials, providing attackers with high-privilege access to the device's Setting Center. This backdoor affects all devices utilizing this dongle, enabling remote attackers to gain significant control over the device without authentication.
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>= 3.6.0.0, < 3.6.0.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the ShineLan-X device on your networkLocate the Growatt ShineLan-X dongle on your network by checking connected devices or reviewing network device inventories. Note its IP address or hostname.Affected if The device exists on your network and is reachable.
-
Access the device web interfaceOpen a web browser and navigate to the IP address of the ShineLan-X device. Log in to the Setting Center or admin panel using your credentials.Affected if You can access the device interface and Settings Center.
-
Check the firmware versionIn the device web interface, look for a firmware version, about page, or system information section. Note the exact version number displayed.Affected if The firmware version is 3.6.0.0, 3.6.0.1, or any version >= 3.6.0.0 and < 3.6.0.2.
-
Verify network exposure of the Setting CenterConfirm that the device web interface is accessible from network segments beyond the local admin network. Check if firewall rules permit access to the device IP from untrusted networks.Affected if The Setting Center is accessible from network segments that are not restricted or isolated.
You are affected if your ShineLan-X firmware version is 3.6.0.0 or 3.6.0.1 and the device interface is network-accessible, since the hardcoded backdoor account exists in these versions.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.6.0.2
Contact Growatt for firmware updates addressing the backdoor credentials; if unavailable, implement network segmentation and restrict external access to the dongle to mitigate exploitation.
Firmware version 3.6.0.2 or later
- Identify the current firmware version of the Growatt ShineLan-X device
- Obtain the firmware version 3.6.0.2 or later from an official Growatt source
- Apply the firmware update following the manufacturer's standard upgrade procedure
- After upgrading, verify the undocumented backup account no longer exists or has been removed
- Confirm the device is running firmware >= 3.6.0.2
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36752 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-36752 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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