CVE-2025-31360
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 trigger device actions associated with specific "scenes" 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 confidenceThis is an authentication/authorization bypass vulnerability in a smart home or IoT device management system. Unauthenticated attackers can send requests to trigger predefined 'scenes' (automated device actions) belonging to any user, without needing valid credentials. The system likely fails to properly validate user identity or ownership before executing scene-triggered device actions.
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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 installationCheck your systems for the Growatt Cloud Portal application. Look for running services on port 8080, 443, or typical web application ports. Check installed software lists or running processes for 'growatt' or 'cloud' related services.Affected if Growatt Cloud Portal software is present and accessible
-
Determine installed versionCheck the version of Growatt Cloud Portal by accessing the login page and looking for version information in the footer, or by querying the API endpoint /api/version. Compare against <= 3.6.0.Affected if Installed version is 3.6.0 or lower
-
Check remote network exposureDetermine if the Growatt Cloud Portal is exposed to the internet or untrusted networks. Review firewall rules, reverse proxy configurations, and port forwards. Check if the portal is accessible from outside the local network.Affected if Portal is reachable from untrusted networks without VPN or proper access controls
-
Verify scene/automation configurationLog into the portal and navigate to the scenes or automation section. Check if any scenes are defined that could be triggered remotely. Look for scenes with device actions like switching inverters, batteries, or other IoT devices.Affected if Any scenes or automated actions are configured in the system
-
Test unauthenticated API accessUsing a tool like curl or Burp, send a request to common scene-trigger API endpoints (such as /api/scene/trigger or similar) without including any authentication headers or session cookies. Observe if the system processes the request.Affected if The system accepts and processes scene trigger requests without authentication credentials
You are affected if Growatt Cloud Portal version 3.6.0 or lower is installed and exposed, with scenes configured, and the system allows unauthenticated scene triggering requests.
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 enforcement and authorization checks to ensure only the legitimate, authenticated user can trigger their own scenes. Validate session tokens and verify user ownership before executing any scene-triggered actions.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-31360 — 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-31360 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