Security readout for executives and security teams
Plain-English summary
GROWI v3.4.6 and earlier contains an open redirect in the login process. An attacker could craft a link that appears to involve a trusted GROWI site but sends the user to another website, enabling phishing. The provided sources do not include CVSS scoring or evidence of active exploitation.
Executive priority
Prioritize remediation for internet-facing or broadly used GROWI instances because this can support phishing against trusted users. Business urgency is moderate unless your environment has high-value credentials or active phishing indicators.
Technical view
The CVE describes a remotely triggerable open redirect affecting WESEEK GROWI v3.4.6 and earlier during login flow handling. The impact is user redirection to arbitrary websites, primarily supporting phishing and credential-theft scenarios. No CWE, CVSS vector, exploit details, or confirmed exploitation are provided in the source bundle.
Likely exposure
Exposure is limited to organizations running WESEEK GROWI v3.4.6 or earlier, especially where the login page is reachable by users or the internet.
Exploitation context
The issue can be abused remotely for phishing by redirecting users from the GROWI login process to attacker-controlled websites. The source bundle does not show KEV listing, public exploitation, or technical exploit details.
Researcher notes
Evidence is sparse: the record names affected versions and the login-process open redirect behavior, but provides no CVSS, CWE, exploit status, or exact fixed version in the supplied bundle. Avoid overstating impact beyond phishing redirection risk.
Mitigation direction
- Inventory GROWI deployments and confirm whether any run v3.4.6 or earlier.
- Review WESEEK and JVN advisories for the vendor-supported fix path.
- Upgrade or apply the vendor correction according to official guidance.
- Warn users to treat unexpected GROWI login links as phishing risk.
- Monitor authentication-related support tickets and reports of suspicious redirects.
Validation and detection
- Confirm the installed GROWI version on each deployment.
- Check whether affected login routes are publicly reachable.
- Review reverse proxy and application logs for unusual login redirect patterns.
- Verify remediation against the WESEEK or JVN advisory, not assumptions.
- Document any remaining affected instances and compensating controls.
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-5969 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.