CVE-2025-27568
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 get users' emails by knowing usernames. A password reset email will be sent in response to this unsolicited request.
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 trigger password reset emails by submitting valid usernames to the password reset function, enabling user enumeration and disclosure of associated email addresses through the reset email itself.
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 versionCheck the portal interface for a version number, typically found in the About section, footer, or account settings. Alternatively, check API response headers or the login page source for version indicators.Affected if The displayed version is 3.6.0 or lower, indicating an unpatched installation.
-
Examine the password reset form inputNavigate to the password reset page on the Growatt Cloud Portal and inspect the input field placeholder text. Check whether it asks for 'Username' or 'Email address'.Affected if The field accepts usernames (e.g., placeholder says 'Enter your username') rather than only accepting email addresses.
-
Test username enumeration vulnerabilitySubmit a known-valid username to the password reset function using curl or browser developer tools. Observe whether a reset email is triggered versus an error message indicating the user does not exist.Affected if Submitting a valid username triggers a password reset email or returns a generic success message without confirming the username does not exist.
-
Verify protection mechanismsCheck the password reset endpoint for CAPTCHA challenges or rate limiting by attempting multiple reset requests. Inspect the page HTML for CAPTCHA widgets or check response headers for rate-limit headers.Affected if No CAPTCHA is present and no rate limiting is enforced on the password reset endpoint.
The environment is affected if the Growatt Cloud Portal version is 3.6.0 or lower and the password reset function accepts usernames instead of only email addresses without CAPTCHA or rate limiting protection.
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 rate limiting, CAPTCHA, or require email addresses instead of usernames for password reset requests to prevent enumeration and block automated abuse.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27568 — 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-27568 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