CVE-2025-61994VulnerabilityPublished 6 Nov 2025

CVE-2025-61994: GROWI · Cross-site scripting (XSS)

Affects GROWISource CVE Database V5

Not known to be exploited · CVSS 5.4 Medium : upgrade to 7.2.10 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.0 base score

5.4Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Changed
Confidentiality: Low
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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to 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 6 Nov 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 2026-10-25.

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 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

Upgrade GROWI to 7.2.10.

Affected software

Product	Affected	Fixed in
GROWI, Inc. GROWI	Affected <7.2.10	Fixed in 7.2.10

AI-suggested

1. Upgrade all GROWI instances to version 7.2.10 or later immediately to apply the official patch addressing this XSS vulnerability. 2. Implement strict user access controls and limit page creation or editing privileges to trusted users only, reducing the risk of malicious content injection. 3. Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers accessing GROWI pages. 4. Conduct regular security audits and code reviews of user-generated content handling to detect and remediate similar injection flaws. 5. Educate users about the risks of clicking on untrusted links or pages within the internal documentation platform. 6. Monitor logs for unusual page creation or modification activities that could indicate exploitation attempts. 7. Consider deploying web application firewalls (WAF) with rules targeting XSS attack patterns specific to GROWI. 8. If upgrading is delayed, temporarily disable or restrict page creation/editing features for non-administrative users as a stopgap measure.

Description

Cross-site scripting vulnerability exists in GROWI prior to v7.2.10. If a malicious user creates a page containing crafted contents, an arbitrary script may be executed on the web browser of a victim user who accesses the page.

Impact

For European organizations, this vulnerability could lead to unauthorized disclosure of sensitive information, session hijacking, and unauthorized actions performed under the victim user's credentials. Organizations using GROWI for internal documentation, project management, or knowledge bases may face risks of data leakage or compromise of user accounts. This is particularly critical in sectors handling confidential or regulated data such as finance, healthcare, government, and critical infrastructure. The attack requires authenticated attacker access, limiting exposure to insider threats or compromised accounts. However, successful exploitation could facilitate lateral movement or privilege escalation within the organization. The lack of availability impact reduces the risk of denial-of-service but does not diminish the confidentiality and integrity concerns. Given no known exploits exist yet, the threat is currently moderate but could escalate if weaponized. European entities with extensive use of GROWI should consider this vulnerability a priority for patching to maintain compliance with data protection regulations like GDPR.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 13 Nov 2025, 05:27 UTC

Technical details

References

Community reviews

Related threats