dbcve.org
GrowiApplication · Weseek

CVE-2023-50294

MEDIUM · 6.5 CVSS v3.1 Published 2023-12-26
Fix available
A fix is available. Upgrade to 6.0.6 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
The App Settings (/admin/app) page in GROWI versions prior to v6.0.6 stores sensitive information in cleartext form. As a result, the Secret access key for external service may be obtained by an attacker who can access the App Settings page.

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

The App Settings page (/admin/app) in GROWI versions prior to v6.0.6 stores sensitive information, including secret access keys for external services, in cleartext rather than using secure encryption or hashing. Any attacker who gains access to the App Settings page can read these plaintext credentials.

MitigationUpgrade to GROWI v6.0.6 or later which addresses the cleartext storage vulnerability, and review access controls to ensure only authorized administrators can access the App Settings page.

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.6

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 GROWI installation version
    Locate the installed GROWI version by checking the package.json file, Docker image tag, or the /_api/v3/version API endpoint if accessible. Alternatively, check the footer of any GROWI page which often displays the version.
    Affected if The installed version is any release prior to v6.0.6 (e.g., v6.0.5, v6.0.0, v5.x, etc.)
  2. Verify App Settings page is accessible
    Navigate to the /admin/app endpoint in the GROWI installation and confirm the page loads. This is the App Settings page where external service configurations are stored.
    Affected if The /admin/app page loads successfully and displays configuration fields without requiring additional authentication beyond standard admin access.
  3. Inspect credential fields for cleartext storage
    On the App Settings page (/admin/app), examine all input fields related to external services such as AWS S3, Slack, Elasticsearch, or other integrated services. Check whether the secret access keys, API keys, or tokens are displayed in plaintext rather than masked or obfuscated.
    Affected if Any secret access keys, API tokens, or credentials are visible as readable text in the input fields or in the page source rather than being masked with dots, asterisks, or placeholder characters.
  4. Check configuration storage for unencrypted secrets
    If database or configuration file access is available, examine the entries where App Settings are stored. Look for any fields containing credential values that appear as plain base64-encoded strings or raw text rather than encrypted values.
    Affected if The database or configuration files contain credential values stored without encryption or hashing applied.

The environment is affected if GROWI version is below v6.0.6 and the App Settings page at /admin/app displays secret access keys or API tokens in plaintext rather than masked or encrypted.

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.6 or later
Fixed in 6.0.6
Interim mitigation

Upgrade to GROWI v6.0.6 or later which addresses the cleartext storage vulnerability, and review access controls to ensure only authorized administrators can access the App Settings page.

Recommended fix High confidence

6.0.6

  1. Upgrade GROWI to version 6.0.6 or later (e.g., latest stable release)
  2. After upgrading, access the App Settings page (/admin/app)
  3. Review all stored secret access keys for external services
  4. Re-save any secret keys if needed to ensure they are stored securely (not in cleartext)
  5. Verify that secret keys are no longer displayed in cleartext on the App Settings page

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

Fix this in Growi Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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