CVE-2025-54806VulnerabilityPublished 23 Oct 2025

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

Affects GROWISource CVE Database V5

Not known to be exploited · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.0 base score

6.1Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 10% 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:C/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
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: 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: 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 23 Oct 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-26.

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

Affected software

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

AI-suggested

1. Upgrade GROWI to the latest version once a patch addressing CVE-2025-54806 is released by the vendor. 2. Until a patch is available, implement strict input validation and output encoding on the page alert function to sanitize URL parameters and prevent script injection. 3. Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts within the GROWI web application. 4. Educate users about the risks of clicking unsolicited or suspicious URLs, especially when logged into internal systems. 5. Monitor web server logs and user activity for unusual URL access patterns indicative of exploitation attempts. 6. Consider deploying web application firewalls (WAFs) with rules designed to detect and block XSS payloads targeting GROWI. 7. Review and limit the permissions of GROWI users to minimize potential damage from compromised accounts. 8. Regularly audit and update security configurations for internal collaboration tools to reduce attack surface.

Description

GROWI v4.2.7 and earlier contains a cross-site scripting vulnerability in the page alert function. If a user accesses a crafted URL while logged in to the affected product, an arbitrary script may be executed on the user's web browser.

Impact

For European organizations, this vulnerability could lead to unauthorized access to sensitive internal documentation and user impersonation within GROWI instances. As GROWI is often used for collaborative knowledge management, exploitation could result in leakage of confidential business information or manipulation of critical operational data. The attack requires a logged-in user to interact with a malicious URL, making phishing or social engineering likely attack vectors. The medium severity indicates moderate risk; however, in sectors with high confidentiality requirements such as finance, healthcare, or government, the impact could be more significant. Additionally, compromised user sessions could facilitate lateral movement or further exploitation within corporate networks. The absence of known exploits reduces immediate risk but does not eliminate the threat, especially as attackers often develop exploits post-disclosure. Organizations with remote or hybrid workforces may be more exposed due to increased URL sharing and external communications.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Oct 2025, 04:39 UTC

Technical details

References

Community reviews

Related threats