Security readout for executives and security teams
Plain-English summary
GROWI v3.4.6 and earlier has a CSRF flaw that could let an attacker abuse an authenticated administrator’s browser to change a user’s Basic Info. Business risk depends on whether exposed GROWI instances are admin-used and reachable. Sources do not provide CVSS or confirmed exploitation.
Executive priority
Treat this as a targeted application-risk cleanup item. It is not KEV-listed, but administrator-session abuse can create meaningful integrity risk if vulnerable GROWI instances remain in use.
Technical view
CVE-2019-5968 affects WESEEK GROWI v3.4.6 and earlier. The reported weakness is cross-site request forgery involving administrator authentication and updates to a user’s Basic Info. The bundle does not include CVSS, CWE mapping, exploit details, or complete fix instructions.
Likely exposure
Organizations running GROWI v3.4.6 or earlier are the exposed population. Risk is higher where administrators access GROWI from browsers that also browse untrusted content.
Exploitation context
The provided sources do not show active exploitation, and the CVE is not marked in KEV. The described attack requires abusing an authenticated administrator’s browser session rather than directly compromising the server without user context.
Researcher notes
Evidence is limited to the CVE description, affected version range, and WESEEK/JVN references. Do not assume broader products, confirmed exploitation, or a specific patch version unless verified in the vendor advisory.
Mitigation direction
- Inventory all GROWI deployments and record installed versions.
- Prioritize instances running GROWI v3.4.6 or earlier.
- Review WESEEK and JVN guidance for fixed versions or vendor workarounds.
- Upgrade beyond affected versions when vendor guidance confirms remediation.
- Limit administrative access to trusted networks where practical.
Validation and detection
- Confirm whether GROWI is present in production, staging, or internal environments.
- Check each GROWI version against the affected range: v3.4.6 and earlier.
- Review administrator workflows for exposure to untrusted browsing while authenticated.
- Check vendor advisories for remediation status before closing the finding.
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.
CVE-2019-5968 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://weseek.co.jp/security/2019/06/04/growi-fix-jvn84876282/CVE reference · x_refsource_MISC
- https://jvn.jp/en/jp/JVN84876282/index.htmlCVE 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.