Unauthenticated charger metadata disclosure via charger ID
Published Apr 15, 2025 · Updated Apr 16, 2025
Authorization bypass in Growatt Cloud portal before 3.6.0 allows remote attackers to read EV charger version and firmware update history. The EV charger information lookup accepts a charger ID as the record key and returns matching version and update-history data without an authorization check. Knowledge of a valid charger ID is the only reported gate, and the documented consequence is read-only disclosure of device metadata.
Summary
What happened
Authorization bypass in Growatt Cloud portal before 3.6.0 allows remote attackers to read EV charger version and firmware update history. The EV charger information lookup accepts a charger ID as the record key and returns matching version and update-history data without an authorization check. Knowledge of a valid charger ID is the only reported gate, and the documented consequence is read-only disclosure of device metadata.
The record
- CVE
- CVE-2025-27575
- Published
- Apr 15, 2025
- Updated
- Apr 16, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-639, T1530
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 15, 2025CVE publishedPublication date reported by the CVE source.
- Apr 16, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo