VulnerabilityPublished 17 Dec 2025

CVE-2025-64700: GROWI · Cross-site Request Forgery (CSRF)

Affects GROWISource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.0 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GROWI, Inc. GROWI	Affected <=7.3.3	Fixed in–

AI-suggested

Upgrade GROWI to the latest version once the vendor releases a patch addressing CVE-2025-64700. Monitor official GROWI channels for patch announcements.
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.
Configure web application security headers such as SameSite cookies to restrict cross-origin requests.
Educate users on the risks of phishing and social engineering attacks that could lead to visiting malicious webpages.
Employ web filtering or endpoint protection solutions to block access to known malicious sites.
Conduct regular security audits and penetration testing focused on CSRF and other web vulnerabilities.
Consider deploying web application firewalls (WAFs) with rules to detect and block suspicious cross-site requests targeting GROWI.
Monitor logs for unusual or unauthorized changes within GROWI to detect potential exploitation attempts early.
Limit user permissions within GROWI to the minimum necessary to reduce the impact of any successful CSRF attack.
Encourage multi-factor authentication (MFA) to reduce the risk of compromised credentials facilitating further attacks.

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.

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.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Dec 2025, 05:55 UTC

Technical details

References

Community reviews

Related threats