dbcve.org
Cloud PortalApplication · Growatt

CVE-2025-24297

CRITICAL · 9.8 CVSS v3.1 Published 2025-04-15
Fix available
A fix is available. Upgrade to after 3.6.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Due to lack of server-side input validation, attackers can inject malicious JavaScript code into users personal spaces of the web portal.

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 confidence

Stored Cross-Site Scripting (XSS) vulnerability in web portal user personal spaces due to missing server-side input validation. Attackers can inject malicious JavaScript that executes when other users view affected personal space content.

MitigationImplement strict server-side input validation with allowlist approach and contextual output encoding for all user-supplied data in personal spaces. Consider Content Security Policy headers as defense-in-depth.

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
Cloud PortalApplication
Affected:<= 3.6.0

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Identify Growatt Cloud Portal version
    Log into the Growatt Cloud Portal admin interface and navigate to Settings or About section to find the software version. Alternatively, check any documentation, release notes, or system inventory that lists the deployed portal version.
    Affected if The installed version is 3.6.0 or lower
  2. Confirm personal spaces feature is active
    Access the user-facing portal and verify if personal spaces or user profile pages are available. Check if regular users can create or edit content in their personal space/profile area.
    Affected if The personal spaces feature exists and users can submit custom content
  3. Inspect user-supplied content storage
    If you have database or backend access, query the data store for user content fields in personal spaces. Look for any HTML or script tags in user-entered data that may indicate injected payloads.
    Affected if User-submitted content in personal spaces is stored and rendered without sanitization

You are affected if the Growatt Cloud Portal version is 3.6.0 or lower AND the personal spaces feature is enabled, allowing users to submit content that gets stored and displayed to others without server-side validation.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 3.6.0
Interim mitigation

Implement strict server-side input validation with allowlist approach and contextual output encoding for all user-supplied data in personal spaces. Consider Content Security Policy headers as defense-in-depth.

Recommended fix Moderate confidence

Upgrade to the latest Cloud Portal release (version > 3.6.0) - consult vendor for exact fixed version

  1. 1. Backup the current Cloud Portal installation and database before making any changes
  2. 2. Check the vendor's official release notes or security advisory for the fixed version (version > 3.6.0)
  3. 3. Download the latest stable release of Cloud Portal from the official vendor source
  4. 4. Deploy the new version in a staging environment first to verify functionality
  5. 5. Apply the upgrade following the vendor's documented upgrade procedure
  6. 6. Verify that the server-side input validation is now properly implemented
  7. 7. Test that XSS payloads are properly sanitized or rejected in user personal spaces
  8. 8. Deploy the updated version to production
Caveat Review vendor release notes for any breaking changes between your current version and the target version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cloud Portal Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24297 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-24297 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