dbcve.org
GrowiApplication · Weseek

CVE-2023-49807

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 when processing the MathJax 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

Stored cross-site scripting vulnerability in GROWI's MathJax processing allows attackers to inject malicious scripts into wiki pages. These scripts persist on the server and execute in the browsers of users who view the affected content.

MitigationUpgrade GROWI to version 6.0.0 or later to remediate 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. Identify installed GROWI version
    Locate the version number of your GROWI installation. This is typically found in the application admin panel under System Information, in a package.json file if you have direct server access, or by checking the Docker image tag if running containerized. Compare this version to the affected range of versions prior to 6.0.0.
    Affected if The installed version is below 6.0.0
  2. Determine if MathJax is enabled
    Check your GROWI configuration settings to see if the MathJax feature is turned on. This is usually found in the admin settings under the Markdown or Rendering section, or in the growi configuration file. MathJax processes mathematical expressions in wiki pages.
    Affected if MathJax rendering is enabled and the GROWI version is below 6.0.0
  3. Inspect wiki pages for suspicious content
    Review recent wiki page edits or pages containing mathematical notation for unexpected script tags, event handlers (onclick, onload, etc.), or javascript: URLs. Check both page content and raw HTML source.
    Affected if Any wiki page contains injected script content that was not authored by legitimate users
  4. Review server logs for exploitation indicators
    Examine GROWI application logs for unusual requests targeting MathJax rendering endpoints, especially those containing HTML or script payloads in parameters related to math expression rendering.
    Affected if Logs show anomalous requests with script injection patterns sent to MathJax processing functions

You are affected if GROWI version is below 6.0.0 AND MathJax is enabled, since the vulnerability exists in the MathJax processing component of these versions.

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 to remediate this vulnerability.

Recommended fix High confidence

6.0.0

  1. Backup your Growi data and configuration before starting the upgrade
  2. Review the official upgrade documentation at weseek.co.jp or docs.growi.org for version 6.0.0 upgrade instructions
  3. Upgrade Growi to version 6.0.0 or later following the documented upgrade procedure
  4. After upgrade, verify the MathJax functionality works correctly and the XSS vulnerability is resolved
Caveat Review release notes for v6.0.0 for any breaking changes or migration requirements

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

Fix this in Growi Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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