dbcve.org
GrowiApplication · Weseek

CVE-2023-49598

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 event handlers of the pre tags in 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 vulnerability in GROWI versions prior to v6.0.0 allows attackers to inject malicious JavaScript through event handlers within pre tags. When users view content containing these crafted pre tags, the embedded script executes in their browsers.

MitigationUpgrade GROWI to version 6.0.0 or later which contains the patch for this vulnerability.

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. Check installed GROWI version
    Locate the package.json or package-lock.json file in your GROWI installation directory and examine the 'version' field, or access the version information through the GROWI web interface (typically found in the footer or at the /_api/v3/version endpoint)
    Affected if The installed version is below v6.0.0 (e.g., v5.x.x, v4.x.x, etc.)
  2. Identify content creation capability
    Verify that user-generated content can be created or edited in your GROWI instance. This includes page creation, comment posting, or any feature that accepts markdown content with pre-formatted text blocks
    Affected if Users or attackers can submit content containing pre tags (using markdown syntax or the editor) and other users can view that content
  3. Confirm pre tag rendering behavior
    Inspect how your GROWI instance renders pre-formatted text blocks (pre tags) in the markdown content. Check whether event handler attributes within pre tags are being sanitized or stripped during rendering
    Affected if Pre tags with inline event handlers (such as onload, onerror, onmouseover) are rendered without sanitization and can execute JavaScript when viewed

Your environment is affected if the installed GROWI version is below v6.0.0 and users can create or view content containing pre tags with potential event handlers.

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 version 6.0.0 or later which contains the patch for this vulnerability.

Recommended fix Moderate confidence

v6.0.0

  1. 1. Back up your Growi data and configuration before proceeding with the upgrade.
  2. 2. Review the Growi v6.0.0 release notes for any specific migration requirements or breaking changes.
  3. 3. Stop the Growi service to prevent data inconsistency during the upgrade.
  4. 4. Upgrade Growi to version 6.0.0 or later using your installation method (e.g., npm, Docker, or package manager).
  5. 5. Verify the upgrade was successful by checking the version number in the admin panel.
  6. 6. Test that the pre tag functionality works correctly and that the XSS vulnerability is no longer present.
  7. 7. Restart the Growi service.
  8. 8. Monitor for any issues and review logs after the upgrade.
Caveat Review v6.0.0 release notes for any breaking changes or migration steps required for your specific setup

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

Fix this in Growi Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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