CVE-2025-54806
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 · uneditedGROWI v4.2.7 and earlier contains a cross-site scripting vulnerability in the page alert function. If a user accesses a crafted URL while logged in to the affected product, an arbitrary script may be executed on the user's web browser.
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 confidenceGROWI v4.2.7 and earlier contains a reflected cross-site scripting (XSS) vulnerability in the page alert function. When a logged-in user visits a specially crafted URL, malicious JavaScript code embedded in the URL is executed in the user's browser context, potentially allowing session hijacking or unauthorized 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< 4.2.8CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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 installed GROWI versionAccess the GROWI administration panel and navigate to the 'About' or 'System Information' page, or check the package.json file in the GROWI installation directory if you have file system accessAffected if The displayed version is 4.2.7 or any version number lower than 4.2.8
-
Locate the page alert functionLog in to GROWI as a user and navigate to any page that supports the alert/notification feature. The vulnerability exists in the page alert function accessible via URL parametersAffected if The page alert function is accessible and accepts user-supplied input in URL parameters such as 'alert' or similar query parameters
-
Verify URL parameter reflectionCraft a test URL with a benign payload in suspected parameters (for example, ?alert=<script>alert('test')</script>) and observe whether the payload is reflected back in the HTML response without encodingAffected if The URL parameter value is reflected verbatim in the page HTML without proper HTML encoding, indicating the XSS vulnerability is present
-
Confirm user session contextEnsure you are testing with a logged-in user account since the vulnerability requires an authenticated session to triggerAffected if Testing is performed while authenticated to GROWI, as the vulnerability is a reflected XSS targeting logged-in users
A user is affected if they are running GROWI version 4.2.7 or earlier and the page alert function reflects unsanitized URL parameters in the response.
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 · scoped4.2.8
Upgrade to a version newer than v4.2.7. If patching is not immediately possible, implement input validation and output encoding in the page alert function to neutralize malicious script injection.
Growi 4.2.8
- Upgrade Growi to version 4.2.8 or later to resolve the XSS vulnerability in the page alert function
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54806 — 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-54806 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