dbcve.org
GrowiApplication · Weseek

CVE-2023-50175

MEDIUM · 5.4 CVSS v3.1 Published 2023-12-26
Fix available
A fix is available. Upgrade to 6.0.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Stored cross-site scripting vulnerability exists in the App Settings (/admin/app) page, the Markdown Settings (/admin/markdown) page, and the Customize (/admin/customize) page of GROWI versions prior to v6.0.0. 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 confidence

Stored cross-site scripting (XSS) vulnerability in GROWI versions before v6.0.0 allows attackers to inject malicious JavaScript through the App Settings (/admin/app), Markdown Settings (/admin/markdown), and Customize (/admin/customize) pages. When administrators access these pages, the stored payload executes in their browsers, potentially enabling session hijacking or privilege escalation.

MitigationUpgrade GROWI to v6.0.0 or later to obtain the security fix. If immediate upgrade is not possible, implement input validation and output encoding on all user-supplied data in the affected admin settings pages.

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
GrowiApplication
Affected:< 6.0.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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify GROWI version
    Check the installed GROWI version in the application. This is typically visible on the landing page, in the admin dashboard, or via the package.json file if self-hosting. Compare your version to the affected range (any version before v6.0.0).
    Affected if Running any version of GROWI below v6.0.0
  2. Confirm admin access is enabled
    Verify that the GROWI application has administrator accounts and that the admin dashboard is accessible. Try navigating to /admin or check if admin functionality is present in the user interface.
    Affected if Administrator accounts exist and admin panel is accessible
  3. Inspect App Settings page for XSS
    Navigate to the App Settings page at /admin/app. Examine all input fields and their saved values for any suspicious JavaScript code or unusual character sequences that may indicate a stored payload.
    Affected if Any unexpected script tags or JavaScript code is found in the saved App Settings values
  4. Inspect Markdown Settings page for XSS
    Navigate to the Markdown Settings page at /admin/markdown. Review all configuration fields and saved values for injected script content or encoded payloads.
    Affected if Any unexpected script tags or JavaScript code is found in the saved Markdown Settings values
  5. Inspect Customize page for XSS
    Navigate to the Customize page at /admin/customize. Check all customization fields including headers, footers, and theme settings for any stored malicious scripts.
    Affected if Any unexpected script tags or JavaScript code is found in the saved Customize settings values

The environment is affected if running GROWI version below v6.0.0 and any of the admin settings pages (/admin/app, /admin/markdown, /admin/customize) contain stored malicious scripts in their saved configuration values.

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 6.0.0 or later
Fixed in 6.0.0
Interim mitigation

Upgrade GROWI to v6.0.0 or later to obtain the security fix. If immediate upgrade is not possible, implement input validation and output encoding on all user-supplied data in the affected admin settings pages.

Recommended fix High confidence

6.0.0

  1. Upgrade GROWI to version 6.0.0 or later
  2. After upgrading, verify the App Settings (/admin/app), Markdown Settings (/admin/markdown), and Customize (/admin/customize) pages no longer allow stored XSS

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

Fix this in Growi Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-50175 — 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-2023-50175 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