Security readout for executives and security teams
Plain-English summary
GROWI versions before 3.5.0 could disclose a page creator's password hash through page metadata API access. A hash is not the password, but it can become dangerous if cracked or reused. The business concern is credential exposure from a wiki system that may contain internal content and user identities.
Executive priority
Treat as a prioritized upgrade if GROWI is internet-facing or accessible by contractors, partners, or broad internal users. It is not marked as actively exploited, but password hash exposure can escalate into account compromise if weak or reused passwords are cracked.
Technical view
The CVE describes improper exposure of a non-public user field in WESEEK GROWI before 3.5.0. A remote user with wiki access could request page metadata and receive the creator's password hash, creating an information disclosure path outside the intended public field set.
Likely exposure
Exposure is limited to organizations running WESEEK GROWI before 3.5.0, especially where untrusted users can access wiki content. The source bundle does not provide CPEs, deployment details, or affected configuration prerequisites beyond wiki access.
Exploitation context
The bundle does not show KEV listing or active exploitation evidence. Public reference material indicates the issue was disclosed, but the provided sources do not establish weaponized exploitation, exploit prevalence, or real-world compromise.
Researcher notes
The CVE record is sparse: no CVSS, CWE, CPE, or detailed patch notes are included in the bundle. Analysis should stay anchored to GROWI before 3.5.0 and password-hash disclosure via page metadata APIs requiring wiki access.
Mitigation direction
- Upgrade WESEEK GROWI to version 3.5.0 or later.
- Review vendor guidance for any additional remediation notes.
- Restrict wiki access to trusted users until upgraded.
- Rotate passwords for exposed page creators if disclosure is suspected.
- Monitor authentication logs for suspicious activity affecting wiki users.
Validation and detection
- Inventory GROWI deployments and confirm whether any are below 3.5.0.
- Verify page metadata responses do not expose password hashes after remediation.
- Review access logs for unusual metadata API activity.
- Identify pages created by high-privilege users for targeted risk review.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
Credential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2019-13338 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://gist.github.com/polkaman/d039fb5236a043907e44efc198d9161cCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.