GrowiApplication · Weseek

CVE-2023-49119

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 via the img tags exists 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

GROWI versions prior to v6.0.0 contain a stored cross-site scripting (XSS) vulnerability in img tag handling. Attackers can inject malicious scripts into img tags that persist on the server and execute in the browsers of users who view the affected content.

MitigationUpgrade GROWI to v6.0.0 or later. Review existing content for any malicious img tag injections that may have been stored prior to patching.

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. Identify installed GROWI version
    Run `npm list growi` in the application directory, check the package.json file, or look at the GROWI admin dashboard under System Information > Version
    Affected if The installed version is prior to v6.0.0 (e.g., v5.x.x, v4.x.x)
  2. Determine if user-generated content is enabled
    Check the GROWI configuration for markdown/HTML rendering settings, typically found in /admin/app-settings or the config.yaml file
    Affected if Users can create or edit pages with markdown or HTML content containing img tags
  3. Inspect stored content for img tag injections
    Query the database (MongoDB) for page content containing img tags, for example: `db.pages.find({ revision: { $regex: '<img' } })` or use the GROWI admin page search
    Affected if Any pages contain img tags with suspicious attributes such as onerror, onload, or javascript: URLs
  4. Check server logs for XSS exploitation attempts
    Review web server and GROWI access logs for patterns like `<img` combined with event handlers or unusual URL schemes
    Affected if Logs contain requests with img tags containing javascript:, onerror, or similar XSS vectors

You are affected if GROWI is installed at a version lower than v6.0.0 AND the platform allows users to create or view content with img tags.

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. Review existing content for any malicious img tag injections that may have been stored prior to patching.

Recommended fix High confidence

6.0.0

  1. Review the current Growi installation and note the current version
  2. Backup the existing Growi database and configuration files
  3. Consult the official GROWI upgrade documentation for upgrading to version 6.0.0
  4. Stop the running GROWI service
  5. Upgrade GROWI to version 6.0.0 using the appropriate method (package manager, Docker, or manual update)
  6. Verify the upgrade was successful by checking the version number
  7. Restart the GROWI service
  8. Test that the application functions correctly and the XSS vulnerability is mitigated

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

Fix this in Growi Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-49119 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