dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-26291

MEDIUM · 5.4 CVSS v3.0 Published 2026-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 GROWI v7.4.6 and earlier. If this vulnerability is exploited, an arbitrary script may be executed in a user's web browser.

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 · moderate confidence

Stored cross-site scripting (XSS) vulnerability in GROWI v7.4.6 and earlier allows attackers to inject malicious JavaScript that persists in the application and executes in the browsers of users who view the contaminated content.

MitigationUpgrade GROWI to a version newer than v7.4.6; apply vendor-released patches for XSS protection and implement output encoding for user-generated content.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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.0/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 the installed GROWI version
    Access the GROWI admin interface and navigate to the 'System Information' or 'About' page, or check the package.json/version file in the GROWI installation directory
    Affected if The displayed version is v7.4.6 or any earlier version (e.g., v7.4.5, v7.4.0, v7.3.x)
  2. Confirm the GROWI service is running
    Verify that the GROWI application is currently operational and accessible via its web URL
    Affected if The application is running and responds to requests
  3. Verify user-generated content input exists
    Log into GROWI as a standard user and check if you can create or edit content using features such as wiki pages, comments, or posts that accept user-supplied text
    Affected if The ability to create or edit user-generated content is enabled and functional
  4. Inspect for existing injected scripts in stored content
    Review the database or use GROWI's search feature to examine stored page content, comments, and user profiles for suspicious script tags, event handlers, or javascript: URLs
    Affected if Any stored content contains unencoded <script> tags, javascript: protocols, or HTML event attributes like onload, onerror, or onclick

A GROWI instance is affected if it runs version v7.4.6 or earlier AND allows user-generated content to be stored, as the stored XSS can persist and execute when other users view the contaminated content.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade GROWI to a version newer than v7.4.6; apply vendor-released patches for XSS protection and implement output encoding for user-generated content.

Have this fixed 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 help mitigating

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-2026-26291 — 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-2026-26291 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