CVE-2025-30257
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 · uneditedUnauthenticated attackers can retrieve serial number of smart meters associated to a specific user account.
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 confidenceAn unauthenticated information disclosure vulnerability allows attackers to retrieve smart meter serial numbers associated with specific user accounts by directly accessing an API endpoint without proper authorization checks.
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.0CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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.
-
Confirm Growatt Cloud Portal deploymentIdentify whether Growatt Cloud Portal is deployed in your environment by reviewing installed web applications, cloud services, or documentation listing your web-facing services.Affected if Growatt Cloud Portal is present in the environment
-
Identify installed versionLocate the version information for your Growatt Cloud Portal installation. This may be found in the application header, about page, administrative console, or by querying the application's API for version metadata.Affected if The installed version is 3.6.0 or lower
-
Locate meter serial number API endpointIdentify API endpoints in the Growatt Cloud Portal that return meter serial numbers or smart meter data. Review API documentation, network traffic logs, or application source code for endpoints related to meters, serial numbers, or user account data.Affected if An API endpoint returning meter serial numbers exists and is accessible
-
Test unauthenticated access to meter endpointAttempt to access the identified meter serial number API endpoint using an HTTP client without providing any authentication credentials, session tokens, or authorization headers.Affected if The endpoint returns meter serial number data without requiring authentication
-
Verify authorization enforcementWith an authenticated session, access the meter serial number API endpoint and confirm that the response is limited to meters associated with that specific user account. Then attempt to access another user's meter data using the same session to check for proper authorization controls.Affected if The endpoint returns data for accounts other than the authenticated user, indicating missing or broken authorization controls
You are affected if Growatt Cloud Portal version 3.6.0 or lower is deployed and the meter serial number API endpoint can be accessed without authentication or returns data for unauthorized user accounts.
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 dataImplement proper authentication and authorization validation on endpoints returning meter serial numbers to ensure only authenticated users with valid session tokens can access account-specific meter data.
- 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-30257 — 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-30257 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