CVE-2025-64700: Cross-site request forgery (CSRF) in GROWI, Inc. GROWI
Cross-site request forgery vulnerability exists in GROWI v7.3.3 and earlier. If a user views a malicious page while logged in, the user may be tricked to do unintended operations.
AI Analysis
Technical Summary
CVE-2025-64700 is a cross-site request forgery (CSRF) vulnerability identified in GROWI, Inc.'s GROWI software, specifically affecting versions 7.3.3 and earlier. CSRF vulnerabilities allow attackers to trick authenticated users into submitting unauthorized requests to a web application without their consent. In this case, if a logged-in user visits a malicious webpage controlled by an attacker, the attacker can cause the user's browser to send crafted requests to the GROWI server, potentially leading to unintended operations such as modifying content or changing settings. The vulnerability does not compromise confidentiality or availability but impacts the integrity of user actions within the application. The CVSS 3.0 score of 4.3 reflects a medium severity, with attack vector being network-based, low attack complexity, no privileges required, but requiring user interaction. The scope remains unchanged, meaning the attack affects only the vulnerable component without impacting other components. No known exploits have been reported in the wild, indicating limited active exploitation at this time. The vulnerability highlights the importance of proper anti-CSRF protections such as synchronizer tokens or same-site cookies in web applications. GROWI is a popular open-source knowledge management and collaboration platform, often used by enterprises and government organizations for internal documentation and knowledge sharing. The presence of this vulnerability could allow attackers to manipulate content or settings if users are tricked into visiting malicious sites, potentially leading to misinformation or disruption of workflows.
Potential Impact
For European organizations, the impact of CVE-2025-64700 depends largely on the extent of GROWI deployment within their environments. Organizations using GROWI for critical documentation, internal knowledge bases, or collaborative workflows could face integrity risks where unauthorized changes are made without user consent. This could lead to misinformation, disruption of business processes, or loss of trust in internal documentation. Since confidentiality and availability are not directly affected, the risk is primarily operational and reputational. The requirement for user interaction (viewing a malicious page) means that phishing or social engineering campaigns could be leveraged to exploit this vulnerability. European entities with large user bases or those in regulated sectors (e.g., finance, government, healthcare) may face compliance risks if unauthorized changes lead to data inaccuracies or operational failures. While no active exploitation is reported, the vulnerability could be weaponized in targeted attacks against high-value organizations using GROWI. The medium severity rating suggests moderate urgency but should not be ignored given the potential for indirect impacts on organizational integrity and workflow reliability.
Mitigation Recommendations
1. Upgrade GROWI to the latest version once the vendor releases a patch addressing CVE-2025-64700. Monitor official GROWI channels for patch announcements. 2. Implement or verify the presence of anti-CSRF tokens (synchronizer tokens) in all state-changing requests within GROWI to ensure requests originate from legitimate users. 3. Configure web application security headers such as SameSite cookies to restrict cross-origin requests. 4. Educate users on the risks of phishing and social engineering attacks that could lead to visiting malicious webpages. 5. Employ web filtering or endpoint protection solutions to block access to known malicious sites. 6. Conduct regular security audits and penetration testing focused on CSRF and other web vulnerabilities. 7. Consider deploying web application firewalls (WAFs) with rules to detect and block suspicious cross-site requests targeting GROWI. 8. Monitor logs for unusual or unauthorized changes within GROWI to detect potential exploitation attempts early. 9. Limit user permissions within GROWI to the minimum necessary to reduce the impact of any successful CSRF attack. 10. Encourage multi-factor authentication (MFA) to reduce the risk of compromised credentials facilitating further attacks.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Belgium, Italy
CVE-2025-64700: Cross-site request forgery (CSRF) in GROWI, Inc. GROWI
Description
Cross-site request forgery vulnerability exists in GROWI v7.3.3 and earlier. If a user views a malicious page while logged in, the user may be tricked to do unintended operations.
AI-Powered Analysis
Technical Analysis
CVE-2025-64700 is a cross-site request forgery (CSRF) vulnerability identified in GROWI, Inc.'s GROWI software, specifically affecting versions 7.3.3 and earlier. CSRF vulnerabilities allow attackers to trick authenticated users into submitting unauthorized requests to a web application without their consent. In this case, if a logged-in user visits a malicious webpage controlled by an attacker, the attacker can cause the user's browser to send crafted requests to the GROWI server, potentially leading to unintended operations such as modifying content or changing settings. The vulnerability does not compromise confidentiality or availability but impacts the integrity of user actions within the application. The CVSS 3.0 score of 4.3 reflects a medium severity, with attack vector being network-based, low attack complexity, no privileges required, but requiring user interaction. The scope remains unchanged, meaning the attack affects only the vulnerable component without impacting other components. No known exploits have been reported in the wild, indicating limited active exploitation at this time. The vulnerability highlights the importance of proper anti-CSRF protections such as synchronizer tokens or same-site cookies in web applications. GROWI is a popular open-source knowledge management and collaboration platform, often used by enterprises and government organizations for internal documentation and knowledge sharing. The presence of this vulnerability could allow attackers to manipulate content or settings if users are tricked into visiting malicious sites, potentially leading to misinformation or disruption of workflows.
Potential Impact
For European organizations, the impact of CVE-2025-64700 depends largely on the extent of GROWI deployment within their environments. Organizations using GROWI for critical documentation, internal knowledge bases, or collaborative workflows could face integrity risks where unauthorized changes are made without user consent. This could lead to misinformation, disruption of business processes, or loss of trust in internal documentation. Since confidentiality and availability are not directly affected, the risk is primarily operational and reputational. The requirement for user interaction (viewing a malicious page) means that phishing or social engineering campaigns could be leveraged to exploit this vulnerability. European entities with large user bases or those in regulated sectors (e.g., finance, government, healthcare) may face compliance risks if unauthorized changes lead to data inaccuracies or operational failures. While no active exploitation is reported, the vulnerability could be weaponized in targeted attacks against high-value organizations using GROWI. The medium severity rating suggests moderate urgency but should not be ignored given the potential for indirect impacts on organizational integrity and workflow reliability.
Mitigation Recommendations
1. Upgrade GROWI to the latest version once the vendor releases a patch addressing CVE-2025-64700. Monitor official GROWI channels for patch announcements. 2. Implement or verify the presence of anti-CSRF tokens (synchronizer tokens) in all state-changing requests within GROWI to ensure requests originate from legitimate users. 3. Configure web application security headers such as SameSite cookies to restrict cross-origin requests. 4. Educate users on the risks of phishing and social engineering attacks that could lead to visiting malicious webpages. 5. Employ web filtering or endpoint protection solutions to block access to known malicious sites. 6. Conduct regular security audits and penetration testing focused on CSRF and other web vulnerabilities. 7. Consider deploying web application firewalls (WAFs) with rules to detect and block suspicious cross-site requests targeting GROWI. 8. Monitor logs for unusual or unauthorized changes within GROWI to detect potential exploitation attempts early. 9. Limit user permissions within GROWI to the minimum necessary to reduce the impact of any successful CSRF attack. 10. Encourage multi-factor authentication (MFA) to reduce the risk of compromised credentials facilitating further attacks.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- jpcert
- Date Reserved
- 2025-11-10T08:39:24.724Z
- Cvss Version
- 3.0
- State
- PUBLISHED
Threat ID: 694231dc364d4dab9cbab4ea
Added to database: 12/17/2025, 4:30:20 AM
Last enriched: 12/24/2025, 5:55:36 AM
Last updated: 2/7/2026, 5:14:29 AM
Views: 77
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.