# CVE-2025-48369: GroupOffice vulnerable to Stored XSS in Tasks Comment Section

> Attackers can execute arbitrary JavaScript in victim browsers via crafted filenames in task comments, potentially stealing sensitive data or hijacking accounts.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 22 May 2025
- **Updated:** 22 May 2025
- **Also known as:** GHSA-45jj-r48j-75pp

## What is CVE-2025-48369?

CVE-2025-48369 is a medium-severity cross-site scripting vulnerability in Intermesh groupoffice, published on 22 May 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Group-Office is an enterprise customer relationship management and groupware tool. Prior to versions 6.8.119 and 25.0.20, a persistent Cross-Site Scripting (XSS) vulnerability exists in Groupoffice's tasks comment functionality, allowing attackers to execute arbitrary JavaScript by uploading an file with a crafted filename. When administrators or other users view the task containing this malicious file, the payload executes in their browser context. The application fails to sanitize image filenames before rendering them in the comment. By uploading an image with a crafted filename containing XSS payloads, attackers can steal sensitive information. Versions 6.8.119 and 25.0.20 contain a fix for the issue.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2025-48369?

It affects 1 product.


Products: Intermesh Group-Office.

## How do I fix CVE-2025-48369?

No fix has been published for CVE-2025-48369 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-48369 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-48369 exists.

## Other vulnerabilities in Intermesh groupoffice

- [CVE-2026-34838](https://insights.sbomify.com/CVE-2026-34838/): Group-Office: Authenticated Remote Code Execution via PHP Insecure Deserialization in `AbstractSettingsCollection` (critical 10.0)
- [CVE-2026-27947](https://insights.sbomify.com/CVE-2026-27947/): Group-Office Vulnerable to Remote Code Execution (RCE) (critical 9.4)
- [CVE-2026-33755](https://insights.sbomify.com/CVE-2026-33755/): Authenticated SQL Injection in Contact/query addressBookIds filter (high 8.8)
- [CVE-2010-3428](https://insights.sbomify.com/CVE-2010-3428/): SQL injection in n/a (high 7.5)
- [CVE-2026-27832](https://insights.sbomify.com/CVE-2026-27832/): Group-Office Has Authenticated SQL Injection in advancedQueryData.comparator (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-48369 and fix it if it is affected.

What it is: CVE-2025-48369 is a medium-severity cross-site scripting vulnerability in Intermesh groupoffice, published on 22 May 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-48369 exists.

Affected product: Intermesh groupoffice. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-48369/ (Markdown: https://insights.sbomify.com/CVE-2025-48369/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-48369
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-48369
- OSV: https://osv.dev/vulnerability/CVE-2025-48369

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-48369/
Summaries are generated and may contain mistakes; the official description above is the record.