Stored XSS via unsanitized task-attachment filenames
Published May 22, 2025 · Updated May 22, 2025
Stored XSS in GroupOffice before 6.8.119 and before 25.0.20 allows remote authenticated users to run JavaScript via crafted image filenames. Task comments render an uploaded image filename through unsafe HTML handling without sanitization or output encoding, preserving the embedded payload. A regular user must attach the crafted file to a task, and execution occurs when another user views the resulting comment, exposing that viewer's browser session data.
Summary
What happened
Stored XSS in GroupOffice before 6.8.119 and before 25.0.20 allows remote authenticated users to run JavaScript via crafted image filenames. Task comments render an uploaded image filename through unsafe HTML handling without sanitization or output encoding, preserving the embedded payload. A regular user must attach the crafted file to a task, and execution occurs when another user views the resulting comment, exposing that viewer's browser session data.
The record
- CVE
- CVE-2025-48369
- Published
- May 22, 2025
- Updated
- May 22, 2025
- Vendor
- Intermesh BV
- Product
- GroupOffice
- Classifications
- CWE-79, T1539
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 22, 2025CVE publishedPublication date reported by the CVE source.
- May 22, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 25.0.20
- Affected versionversion=< 6.8.119
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Vendor advisory reproduction stepsproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo