Security readout for executives and security teams
Plain-English summary
Older WESEEK GROWI sites before 3.5.0 could let visitors bypass site-wide basic authentication through an API-related URL parameter. If a private wiki relied on that basic-auth gate, unauthenticated users may have been able to browse it. The sources do not provide CVSS scoring or confirmed exploitation.
Executive priority
Prioritize remediation if GROWI protected sensitive internal wiki content or was reachable from the internet. The issue can undermine the main access gate, but available sources do not show active exploitation or severity scoring.
Technical view
CVE-2019-13337 is a basic-authentication bypass in WESEEK GROWI before 3.5.0. The backend did not validate the API access-token URL parameter before treating basic authentication as unnecessary, allowing normal website browsing without a valid token. Public records do not list detailed affected CPEs, CVSS, or CWEs.
Likely exposure
Exposure is most relevant for GROWI instances before 3.5.0 that enabled site-wide basic authentication, especially internet-facing or partner-accessible knowledge bases containing internal documentation.
Exploitation context
The CVE record describes a simple authentication bypass condition, but CISA KEV is false and the provided sources do not confirm active exploitation, exploit maturity, or attacker use in the wild.
Researcher notes
The public record is sparse: no CVSS vector, CWE, CPE, or detailed vendor advisory is included in the supplied bundle. Analysis is based on the CVE description and linked public reference. Treat product/version scoping beyond GROWI before 3.5.0 as unconfirmed.
Mitigation direction
- Upgrade GROWI to version 3.5.0 or later.
- Review WESEEK GROWI advisories and release notes for supported remediation guidance.
- Restrict external access to affected GROWI instances until upgraded.
- Avoid relying on site-wide basic authentication as the only protection for sensitive wiki content.
- Review logs for unexpected unauthenticated browsing of private pages.
Validation and detection
- Inventory all GROWI deployments and record their versions.
- Confirm whether site-wide basic authentication is enabled on each instance.
- Check whether any deployed instance is older than 3.5.0.
- Verify upgraded instances no longer bypass basic authentication via API-token URL handling.
- Review access logs for suspicious anonymous access before remediation.
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-13337 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.