CVE-2023-50339
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 · uneditedStored cross-site scripting vulnerability exists in the User Management (/admin/users) page of GROWI versions prior to v6.1.11. If this vulnerability is exploited, an arbitrary script may be executed on the web browser of the user who accessed the site using the product.
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 confidenceA stored cross-site scripting (XSS) vulnerability exists in the User Management page (/admin/users) of GROWI prior to version 6.1.11. The vulnerability allows attackers to inject malicious scripts that persist on the page and execute in the browsers of users who access the admin users interface.
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< 6.1.11CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 GROWI installationLocate the GROWI installation directory and look for version information in package.json, or query the running instance via the /_api/v3/version endpointAffected if GROWI is not found or version cannot be determined
-
Determine installed GROWI versionRead the version field from package.json in the GROWI installation root, or retrieve it from the API endpoint /_api/v3/versionAffected if The version number is present and is less than 6.1.11 (e.g., 6.1.10, 6.0.0, etc.)
-
Verify admin interface is accessibleConfirm that the /admin/users endpoint is reachable by attempting to access it with appropriate admin credentials, or check if the admin panel is enabled in the configurationAffected if The admin users management page is accessible and functional
-
Inspect user data for injected scriptsQuery the user database or user collection for any user entries containing HTML or JavaScript patterns in fields that are displayed on the /admin/users page (such as username, name, or email fields)Affected if User records contain unsanitized script tags or HTML containing event handlers (onclick, onerror, etc.) in fields shown in the admin user list
You are affected if GROWI version is below 6.1.11 and the admin user management interface is accessible, particularly if suspicious script content is found in user profile fields.
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 · scoped6.1.11
Upgrade GROWI to version v6.1.11 or later, which contains the fix for this stored XSS vulnerability in the admin user management functionality.
v6.1.11
- 1. Back up your current GROWI data and configuration
- 2. Stop the GROWI service
- 3. Upgrade GROWI to version 6.1.11 or later
- 4. Verify the upgrade was successful
- 5. Restart the GROWI service
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2023-50339 — 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-2023-50339 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