CVE-2025-36751
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 · uneditedEncryption is missing on the configuration interface for Growatt ShineLan-X and MIC 3300TL-X. This allows an attacker with access to the network to intercept and potentially manipulate communication requests between the inverter and its cloud endpoint.
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 and MIC 3300TL-X inverters have no encryption enabled on their configuration interface, allowing network-adjacent attackers to perform man-in-the-middle attacks and intercept or manipulate data flowing between the inverter and its cloud endpoint.
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
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 Growatt inverter models on the networkCheck network inventory or physically locate inverters to determine if models ShineLan-X or MIC 3300TL-X are present. These are solar inverters with built-in web configuration interfaces.Affected if The environment contains Growatt ShineLan-X or MIC 3300TL-X inverter models.
-
Access the inverter web configuration interfaceOpen a web browser and navigate to the inverter's IP address (found via network scan or inverter display). Look for the security or network settings page within the configuration panel.Affected if The configuration interface is accessible without encryption (HTTP instead of HTTPS).
-
Verify encryption settings in configurationLocate the network or communication settings section. Check whether encryption, TLS, or HTTPS options are present, enabled, or available for the cloud communication link.Affected if Encryption is disabled, not configured, or unavailable in the settings.
-
Capture network traffic to cloud endpointUse a packet capture tool (such as Wireshark or tcpdump) on the network segment between the inverter and its cloud destination. Inspect the traffic for unencrypted protocols or plaintext data.Affected if Traffic to the inverter's cloud endpoint (typically on ports 80/HTTP or other non-TLS ports) is transmitted in plaintext.
The environment is affected if Growatt ShineLan-X or MIC 3300TL-X inverters have no encryption (HTTPS/TLS) enabled on their configuration interface, resulting in unencrypted communications that could be intercepted via man-in-the-middle attacks.
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.
From vendor dataEnable TLS/HTTPS encryption on the device configuration interface if supported, or implement network segmentation and VPN access to protect communications; isolate inverters from untrusted networks.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-36751 — 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-36751 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