CVE-2025-27561
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 rename "rooms" of arbitrary users.
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 confidenceUnauthenticated attackers can rename rooms belonging to arbitrary users due to missing or insufficient authorization checks. This appears to be an Insecure Direct Object Reference (IDOR) or broken access control vulnerability where the application fails to validate that the requesting user has permission to modify the targeted room.
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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 is in useIdentify whether your environment hosts or uses the Growatt Cloud Portal service. Check running services, installed packages, or documentation that references this product.Affected if Growatt Cloud Portal is not present in your environment, this CVE does not apply.
-
Check installed versionLocate the installed version of Growatt Cloud Portal. This may be found in the application UI under 'About' or 'Version', in configuration files, or via API endpoint that returns version information. Compare your version to the affected range: <= 3.6.0Affected if Your installed version is 3.6.0 or lower.
-
Identify room management functionalityLocate the room renaming feature in the application. This is typically found in the device/room management section where users can create, edit, or delete rooms. Determine if an API endpoint exists for renaming rooms (often a PUT or POST request to /room/{id}/rename or similar).Affected if The room renaming feature is not accessible or does not exist, the vulnerability cannot be exploited.
-
Test for missing authorization on room renameSend a request to the room rename endpoint without valid authentication credentials or with a different user's session token, attempting to modify a room ID that does not belong to the authenticated user. Observe if the request succeeds despite lacking ownership.Affected if The request succeeds and the room is renamed without proper ownership validation, indicating the vulnerability is present.
You are affected if Growatt Cloud Portal version 3.6.0 or lower is in use AND the room renaming endpoint can be invoked without proper ownership validation.
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 ownership validation to ensure users can only rename rooms they own. Add explicit authorization checks before processing room modification requests.
- 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-27561 — 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-27561 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