Incorrect AuthorizationWeakness · CWE-863

CVE-2025-29757

CRITICAL · 9.4 CVSS v4.0 Published 2025-07-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
An incorrect authorisation check in the the 'plant transfer' function of the Growatt cloud service allowed a malicous attacker with a valid account to transfer any plant into his/her account.

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 confidence

Broken access control vulnerability in Growatt cloud service's plant transfer function. The function fails to properly verify that the requesting user has authorization to transfer a specific plant, allowing any authenticated user to arbitrarily transfer ownership of any plant to their own account through the flawed authorization check.

MitigationThe vendor must implement proper authorization validation in the plant transfer function to ensure users can only transfer plants they own or have been granted permission to manage. Until the vendor releases a patch, users should monitor account activity for unauthorized plant transfers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Low
Authentication
X
User interaction
None
Scope
P

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:P/AU:X/R:X/V:C/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Growatt cloud service usage
    Identify if your solar monitoring setup uses Growatt's cloud service (inverter data flows through server.growatt.com or similar Growatt cloud endpoints)
    Affected if Your system relies on Growatt's cloud platform for plant management and monitoring
  2. Identify your registered plant IDs
    Log into your Growatt cloud account and navigate to the plant management section to list all plant IDs associated with your account
    Affected if You have one or more plants registered in your Growatt cloud account
  3. Test plant transfer function ownership validation
    Attempt a plant transfer API request to the transfer endpoint using a plant ID that does NOT belong to your account (but is valid on the platform), observing whether the system accepts the transfer without rejecting it for ownership violation
    Affected if The transfer request succeeds or returns a success status for a plant you do not own, indicating the ownership check is missing
  4. Review account activity logs for plant transfers
    Access your Growatt account audit logs or activity history and search for any plant transfer operations you did not initiate, particularly transfers TO or FROM your account
    Affected if Plant transfer records exist that you did not authorize or that moved plants you did not previously own into your account without action on your part
  5. Check for unexpected plant ownership changes
    Compare your current plant list against any known previous records or backups of your account to identify plants that were added or removed without your action
    Affected if Your account shows plants you did not create or is missing plants you did not transfer away

Your environment is affected if you use Growatt's cloud service and the plant transfer function allows transferring plants you do not own, or if unauthorized plant transfers appear in your account activity.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

The vendor must implement proper authorization validation in the plant transfer function to ensure users can only transfer plants they own or have been granted permission to manage. Until the vendor releases a patch, users should monitor account activity for unauthorized plant transfers.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,920.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-29757 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-29757 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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