Skip to main content
CVE-2025-36754VulnerabilityPublished Updated

CVE-2025-36754: Growatt ShineLan-X · Authentication Bypass by Spoofing

Affects Growatt ShineLan-XSource CVE Database V5

0

Not known to be exploited · CVSS 9.3 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:H/SI:H/SA:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Growatt ShineLan-XAffected
  • =3.6.0.0
Fixed in–

AI-suggested

1. Immediately isolate affected Growatt ShineLan-X devices from untrusted networks to limit exposure. 2. Implement strict network segmentation to restrict device access only to authorized personnel and systems. 3. Monitor network traffic for unusual DNS queries or configuration changes indicative of exploitation attempts. 4. Enforce strong access controls and authentication mechanisms at the network level, such as VPNs or zero-trust models, until a vendor patch is available. 5. Regularly audit device configurations and logs to detect unauthorized changes early. 6. Engage with Growatt support channels to obtain firmware updates or patches addressing this vulnerability as soon as they are released. 7. Consider deploying intrusion detection/prevention systems (IDS/IPS) tuned to detect anomalous POST requests targeting device management interfaces. 8. Educate operational technology (OT) and IT teams about this vulnerability to ensure rapid incident response readiness. 9. Where possible, replace or upgrade devices that cannot be patched promptly to minimize risk exposure.

Description

The authentication mechanism on web interface is not properly implemented. It is possible to bypass authentication checks by crafting a post request with new settings since there is no session token or authentication in place. This would allow an attacker for instance to point the device to an arbitrary address for domain name resolution to e.g.facililitate a man-in-the-middle (MitM) attack.

References

Community reviews

Loading reviews…