CVE-2025-24315
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 add devices of other users to their scenes (or arbitrary scenes of other 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 · high confidenceThis is an IDOR (Insecure Direct Object Reference) authorization bypass vulnerability where unauthenticated attackers can manipulate scene-device relationships across user accounts. The application fails to verify that the authenticated user owns the target scene before allowing device associations, enabling an attacker to associate any user's devices with any scene.
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.
-
Identify Growatt Cloud Portal deploymentInventory your environment for installations of the Growatt Cloud Portal application, checking running services, installed packages, or web application fingerprintsAffected if Growatt Cloud Portal is deployed in the environment
-
Determine installed versionCheck the application version through the web interface footer, admin panel, or by querying the API endpoint for version information (commonly /api/version or in server headers)Affected if The version is 3.6.0 or lower
-
Verify authentication on scene endpointsAttempt to access scene-related API endpoints (such as /api/scenes, /api/scene/devices, or similar) without providing valid authentication credentialsAffected if The endpoints respond without requiring authentication (200 OK responses instead of 401/403)
-
Test IDOR on scene-device associationsIf authenticated, create a scene and attempt to associate devices from a different user account by manipulating scene ID or device ID parameters in API requestsAffected if Device associations succeed without proper ownership validation (the request succeeds when it should fail with 403)
If Growatt Cloud Portal version 3.6.0 or lower is in use AND the scene manipulation endpoints are accessible without proper authentication, the environment is affected by this IDOR vulnerability.
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.
dbcve · scopedImplement proper authorization checks verifying user ownership before allowing scene-device modifications, and enforce authentication requirements for all scene manipulation endpoints.
Cloud Portal > 3.6.0 (latest stable release)
- 1. Identify the current Cloud Portal version in use by checking the application administration interface or system inventory
- 2. Upgrade Cloud Portal to a version higher than 3.6.0 (preferably the latest stable release)
- 3. After upgrade, verify that authentication and authorization controls are functioning correctly
- 4. Review access control logs to confirm no unauthorized device/scene modifications occurred prior to patching
- 5. Implement additional monitoring for device and scene manipulation API endpoints
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24315 — 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-24315 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