CVE-2025-24487
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 attacker can infer the existence of usernames in the system by querying an 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 · high confidenceAn unauthenticated attacker can enumerate valid usernames in the system by querying an API endpoint that reveals whether a username exists, enabling credential stuffing or brute force attacks.
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 versionLocate the installed version of Growatt Cloud Portal in the application admin panel, system information page, or installation files. Check for a version file or banner typically found in /opt/growatt or the application root directory.Affected if The installed version is 3.6.0 or lower.
-
Confirm API endpoint exposureIdentify the API endpoint used for user authentication or registration. Common paths include /api/user/login, /api/user/register, or similar paths under /api/. Inspect web server logs or proxy configurations to determine if these endpoints are accessible from unauthenticated network paths.Affected if The user-related API endpoints are exposed without authentication requirements.
-
Inspect API response differentiationCapture and compare API responses when submitting requests with both valid and invalid usernames. Examine HTTP status codes, error messages, and response times for differences. Look for responses that explicitly confirm username existence versus generic error messages.Affected if API responses clearly indicate whether a username exists (e.g., 'Username not found' vs 'Invalid password') rather than returning identical messages for both valid and invalid usernames.
-
Review access logs for enumeration patternsExamine web server or application access logs for repeated API requests with varying usernames from the same source IP. Look for patterns of sequential username probes or high-volume authentication attempts targeting the user lookup endpoint.Affected if Logs show repeated requests checking username validity from single or multiple source IPs without corresponding successful logins.
The environment is affected if Growatt Cloud Portal version is 3.6.0 or lower AND the user enumeration API endpoint is accessible and returns distinct responses for valid versus invalid usernames.
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 generic error responses that do not differentiate between invalid and valid usernames, combined with rate limiting and account lockout policies to prevent automated enumeration.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24487 — 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-24487 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