CVE-2025-27929
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 full list of users associated with arbitrary accounts.
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 confidenceThis is an information disclosure vulnerability where unauthenticated attackers can enumerate all users associated with arbitrary accounts, likely due to broken access control or insecure direct object reference (IDOR) in user listing endpoints.
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 Growatt Cloud Portal installationReview your infrastructure inventory or search for services running on common ports (ports 80, 443, 8080) that respond with Growatt-related branding, headers, or URLs containing 'growatt' or 'cloudportal'. Check network diagrams or asset management records for this application.Affected if Growatt Cloud Portal is deployed in the environment
-
Determine installed versionCheck the application footer, about page, or login screen for a version number. Alternatively, examine HTTP response headers or API endpoints for version information (e.g., /api/version, /about). Compare against the affected range <= 3.6.0.Affected if The installed version is 3.6.0 or lower
-
Verify user listing API endpoints existLocate the user management API endpoints by reviewing application documentation, inspecting network traffic during legitimate use, or checking for common patterns such as /api/users, /api/userlist, /admin/users, or /account/users. Document which endpoints expose user data.Affected if User listing endpoints exist in the application
-
Test endpoint accessibility without authenticationFrom an unauthenticated context (incognito browser or non-authenticated API client), attempt to access the identified user listing endpoints. Check if the server returns user data or user lists without requiring login credentials.Affected if User list data is returned without authentication being required
-
Review access logs for enumeration indicatorsSearch web server, application, or proxy logs for repeated requests to user-related endpoints from unauthenticated IPs, especially patterns indicating user enumeration (varying user IDs or account parameters). Look for 200 responses to these unauthenticated requests.Affected if Logs show successful unauthenticated access to user enumeration endpoints
If Growatt Cloud Portal version 3.6.0 or lower is in use and user listing endpoints are accessible without authentication, the environment is affected by this CVE.
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 checks to ensure users can only view user lists for accounts they are authorized to access.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27929 — 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-27929 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