CVE-2025-27927
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 · uneditedAn unauthenticated attackers can obtain a list of smart devices by knowing a valid username through an unprotected API.
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 confidenceAn unprotected API endpoint in a smart device management system allows unauthenticated attackers to enumerate and retrieve a list of smart devices associated with a valid username. The vulnerability stems from missing authentication and authorization checks on an API that should require valid user credentials.
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.
-
Identify installed Growatt Cloud Portal versionAccess the portal's main interface and look for version information in the footer, about page, or help section. Alternatively, inspect HTTP response headers from API requests for version indicators.Affected if The installed version is 3.6.0 or lower.
-
Locate the device listing API endpointReview web application traffic while logged into the portal to identify the endpoint used to fetch smart device data. Common patterns include /api/devices, /device/list, or /v1/devices.Affected if The endpoint exists and is reachable over the network.
-
Test unauthenticated access to the device APISend an HTTP request to the identified device listing endpoint without including any authentication tokens, session cookies, or credentials in the request.Affected if The API returns device data or a valid response without requiring authentication.
-
Attempt username-based device enumerationSend a request to the device API with a known valid username but without authentication credentials, observing if devices associated with that username are returned.Affected if The API returns device information for the specified username without any authentication.
A user is affected if the Growatt Cloud Portal version is 3.6.0 or lower AND the device listing API endpoint responds to unauthenticated requests with device data.
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 · scopedImplement proper authentication and authorization checks on the API endpoint to ensure only authenticated and authorized users can access device listings. Additionally, consider rate limiting to prevent enumeration attacks.
Cloud Portal 3.6.1 or later
- Identify the current Cloud Portal version in use by checking the application's version endpoint or administrative interface
- Contact the vendor (Cloud Portal provider) to obtain the specific patched version that addresses CVE-2025-27927
- Upgrade Cloud Portal to version 3.6.1 or later (the first version containing the security fix)
- After upgrade, verify the API endpoint previously vulnerable is now protected and requires proper authentication
- Confirm that unauthenticated requests to enumerate smart devices are now rejected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27927 — 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-27927 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