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 versions 7.3.3 and earlier. CSRF vulnerabilities allow attackers to trick authenticated users into submitting unauthorized requests to a web application, leveraging the user's active session and privileges. In this case, if a logged-in user visits a maliciously crafted webpage, the attacker can induce the user’s browser to perform unintended operations on the GROWI platform without their knowledge or consent. The vulnerability does not require the attacker to have any privileges or to bypass authentication, but it does require the victim to interact with a malicious page (user interaction). The CVSS 3.0 base score is 4.3, reflecting a medium severity level, with the vector indicating network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:N), user interaction required (UI:R), unchanged scope (S:U), no confidentiality impact (C:N), low integrity impact (I:L), and no availability impact (A:N). Although no known exploits are reported in the wild, the vulnerability poses a risk of unauthorized data modification or unintended actions within GROWI. The lack of patch links suggests that a fix may be pending or not yet publicly available. Organizations using affected versions should be aware of this threat and prepare to apply patches or mitigations promptly.
Potential Impact
For European organizations, the primary impact of this CSRF vulnerability lies in the potential unauthorized modification of data or execution of unintended operations within the GROWI collaborative platform. This can lead to data integrity issues, such as unauthorized content changes or configuration modifications, which may disrupt workflows or cause misinformation. Since GROWI is often used for internal documentation and knowledge sharing, compromised integrity could affect decision-making and operational efficiency. The vulnerability does not directly compromise confidentiality or availability, but indirect effects such as loss of trust or operational delays could occur. Organizations in sectors with high reliance on collaborative documentation—such as technology firms, research institutions, and government agencies—may face higher risks. Additionally, the requirement for user interaction means that phishing or social engineering campaigns could be leveraged to exploit this vulnerability, increasing the threat surface. The absence of known exploits reduces immediate risk but does not eliminate the need for proactive measures.
Mitigation Recommendations
To mitigate CVE-2025-64700, European organizations should: 1) Monitor GROWI vendor announcements closely and apply security patches promptly once released for versions 7.3.3 and earlier. 2) Implement or verify the presence of anti-CSRF tokens in all state-changing requests within GROWI to prevent unauthorized request forgery. 3) Employ Content Security Policy (CSP) headers and SameSite cookie attributes to reduce the risk of CSRF attacks. 4) Educate users about the risks of clicking on suspicious links or visiting untrusted websites while logged into GROWI, emphasizing phishing awareness. 5) Restrict browser sessions and implement session timeout policies to limit the window of opportunity for exploitation. 6) Consider network-level protections such as web application firewalls (WAFs) with rules to detect and block CSRF attack patterns. 7) Conduct internal security reviews and penetration testing focused on web application vulnerabilities to identify and remediate similar issues proactively.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Denmark, Belgium
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 versions 7.3.3 and earlier. CSRF vulnerabilities allow attackers to trick authenticated users into submitting unauthorized requests to a web application, leveraging the user's active session and privileges. In this case, if a logged-in user visits a maliciously crafted webpage, the attacker can induce the user’s browser to perform unintended operations on the GROWI platform without their knowledge or consent. The vulnerability does not require the attacker to have any privileges or to bypass authentication, but it does require the victim to interact with a malicious page (user interaction). The CVSS 3.0 base score is 4.3, reflecting a medium severity level, with the vector indicating network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:N), user interaction required (UI:R), unchanged scope (S:U), no confidentiality impact (C:N), low integrity impact (I:L), and no availability impact (A:N). Although no known exploits are reported in the wild, the vulnerability poses a risk of unauthorized data modification or unintended actions within GROWI. The lack of patch links suggests that a fix may be pending or not yet publicly available. Organizations using affected versions should be aware of this threat and prepare to apply patches or mitigations promptly.
Potential Impact
For European organizations, the primary impact of this CSRF vulnerability lies in the potential unauthorized modification of data or execution of unintended operations within the GROWI collaborative platform. This can lead to data integrity issues, such as unauthorized content changes or configuration modifications, which may disrupt workflows or cause misinformation. Since GROWI is often used for internal documentation and knowledge sharing, compromised integrity could affect decision-making and operational efficiency. The vulnerability does not directly compromise confidentiality or availability, but indirect effects such as loss of trust or operational delays could occur. Organizations in sectors with high reliance on collaborative documentation—such as technology firms, research institutions, and government agencies—may face higher risks. Additionally, the requirement for user interaction means that phishing or social engineering campaigns could be leveraged to exploit this vulnerability, increasing the threat surface. The absence of known exploits reduces immediate risk but does not eliminate the need for proactive measures.
Mitigation Recommendations
To mitigate CVE-2025-64700, European organizations should: 1) Monitor GROWI vendor announcements closely and apply security patches promptly once released for versions 7.3.3 and earlier. 2) Implement or verify the presence of anti-CSRF tokens in all state-changing requests within GROWI to prevent unauthorized request forgery. 3) Employ Content Security Policy (CSP) headers and SameSite cookie attributes to reduce the risk of CSRF attacks. 4) Educate users about the risks of clicking on suspicious links or visiting untrusted websites while logged into GROWI, emphasizing phishing awareness. 5) Restrict browser sessions and implement session timeout policies to limit the window of opportunity for exploitation. 6) Consider network-level protections such as web application firewalls (WAFs) with rules to detect and block CSRF attack patterns. 7) Conduct internal security reviews and penetration testing focused on web application vulnerabilities to identify and remediate similar issues proactively.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
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/17/2025, 4:45:16 AM
Last updated: 12/18/2025, 12:46:43 PM
Views: 27
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.
Related Threats
CVE-2025-14618: CWE-862 Missing Authorization in listingthemes Sweet Energy Efficiency
MediumCVE-2025-14437: CWE-532 Insertion of Sensitive Information into Log File in wpmudev Hummingbird Performance – Cache & Page Speed Optimization for Core Web Vitals | Critical CSS | Minify CSS | Defer CSS Javascript | CDN
HighCVE-2025-14277: CWE-918 Server-Side Request Forgery (SSRF) in bdthemes Prime Slider – Addons for Elementor
MediumCVE-2025-13110: CWE-639 Authorization Bypass Through User-Controlled Key in realmag777 HUSKY – Products Filter Professional for WooCommerce
MediumCVE-2025-10910: CWE-639 Authorization Bypass Through User-Controlled Key in Govee H6056
CriticalActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.