CVE-2019-13338
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 · uneditedIn WESEEK GROWI before 3.5.0, a remote attacker can obtain the password hash of the creator of a page by leveraging wiki access to make API calls for page metadata. In other words, the password hash can be retrieved even though it is not a publicly available field.
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 confidenceIn WESEEK GROWI before 3.5.0, the wiki's API for page metadata inadvertently exposes the password hash of the page creator. A remote attacker with wiki access can retrieve these hashes through API calls, enabling offline password cracking.
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< 3.5.0CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed GROWI versionLocate the GROWI installation and check its version number. This is typically found in the package.json file at the application root, in the admin dashboard under System Information, or by querying the /_api/version API endpoint if available.Affected if The installed version is any release prior to 3.5.0 (e.g., 3.4.x, 3.3.x, etc.)
-
Verify API access is enabledConfirm that the wiki is accessible to users. The vulnerability requires a remote attacker to have at least low-privilege wiki access to make API calls. Check that user registration or guest access is enabled.Affected if The wiki allows user accounts or guest access, enabling external API requests.
-
Inspect page metadata API responseMake an authenticated or guest request to the page metadata API endpoint (typically endpoints like /api/pages or /_api/pages/{pageId} that return page creator information). Examine the JSON response for any field containing password hash data associated with the page creator.Affected if The API response includes a password hash, bcrypt hash, or any credential-related field in the creator or author metadata.
-
Check for credential fields in user objectReview the raw JSON payload returned by page-related API calls. Look specifically for fields such as 'password', 'passwordHash', 'hash', 'hashedPassword', or similar strings within the user object attached to page metadata.Affected if Any field in the API output contains a bcrypt or hashed representation of a password.
You are affected if running GROWI version 3.5.0 or earlier AND the page metadata API endpoint is accessible and returns password hash values in the creator user object.
Generated from the published advisory. Verify against your own configuration.
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 data3.5.0
Upgrade to GROWI 3.5.0 or later to receive the patch that removes password hashes from API responses.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2019-13338 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-13338 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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