# CVE-2025-7618: A stored Cross-Site Scripting (XSS) vulnerability exists in the File Explorer and Text Editor of ADM

> Attackers can inject malicious scripts into ADM File Explorer and Text Editor to steal cookies and sensitive browser data.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Jul 2025
- **Updated:** 14 Jul 2025
- **Also known as:** GHSA-vcwx-v3cx-wrxp

## What is CVE-2025-7618?

CVE-2025-7618 is a medium-severity cross-site scripting vulnerability in ASUSTOR ADM, published on 14 Jul 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A stored Cross-Site Scripting (XSS) vulnerability vulnerability was found in the File Explorer and Text Editor of ADM. An attacker could exploit this vulnerability to inject malicious scripts into the applications, which may then access cookies or other sensitive information retained by the browser and used with the affected applications.
Affected products and versions include: from ADM 4.1.0 to ADM 4.3.3.RH61 as well as ADM 5.0.0.RIN1 and earlier, and Text Editor 1.0.0.r112 and earlier.

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

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


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

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

## Is CVE-2025-7618 being exploited?

There is no known exploitation of CVE-2025-7618 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-7618 is a medium-severity cross-site scripting vulnerability in ASUSTOR ADM, published on 14 Jul 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-7618 in the wild and no public exploit code.

Affected product: ASUSTOR ADM. 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-7618/ (Markdown: https://insights.sbomify.com/CVE-2025-7618/index.md)
```

## Sources

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

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