CVE-2025-31949
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 authenticated attacker can obtain any plant name by knowing the plant ID.
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 Insecure Direct Object Reference (IDOR) vulnerability where an authenticated user can access plant name records by directly manipulating the plant ID parameter. The application fails to validate that the authenticated user has authorization to access the specific plant record before returning the data.
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 installationDetermine if your environment includes the Growatt Cloud Portal web application. Check installed software listings or consult your system documentation for the presence of this solar monitoring platform.Affected if The Growatt Cloud Portal is not present in your environment.
-
Check installed versionLocate the version information for your Growatt Cloud Portal installation. This is typically found in the application about page, system settings, or by examining the application metadata files. Compare your version number to the affected range of <= 3.6.0.Affected if Your installed version is 3.6.0 or lower.
-
Verify plant monitoring feature is accessibleConfirm that the plant name records feature is enabled and accessible within the portal. This typically involves logging in as an authenticated user and navigating to the plant monitoring or dashboard section where plant records are displayed.Affected if The plant monitoring feature is not available or you cannot authenticate to the portal.
-
Test for IDOR via plant ID parameter manipulationUsing an authenticated session, access a plant record you are authorized to view. Then attempt to modify the plant ID parameter in the request (such as in the URL query string or API call) to reference a different plant ID that you do not own or have permission to access. Observe whether the application returns data for the unauthorized plant record without proper authorization validation.Affected if The application returns plant record data for unauthorized plant IDs without rejecting the request.
You are affected if you are running Growatt Cloud Portal version 3.6.0 or lower and the plant monitoring feature is accessible to authenticated users, particularly if unauthorized plant ID manipulation returns data.
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 authorization checks to verify the authenticated user has permission to access the requested plant record before returning any data. Consider adding object-level access control validation in the data retrieval logic.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-31949 — 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-31949 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