# CVE-2025-7699: An improper access control vulnerability was found in the EZ Sync Manager of ADM

> Authenticated users can copy arbitrary readable files from the server to their folder due to missing authorization checks, exposing sensitive data.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/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:** Not needed
- **Fix available:** No
- **Published:** 16 Jul 2025
- **Updated:** 16 Jul 2025
- **Also known as:** GHSA-rg2c-ffr7-g2v8

## What is CVE-2025-7699?

CVE-2025-7699 is a high-severity missing authorization vulnerability in ASUSTOR ADM, published on 16 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An improper access control vulnerability  was found in the EZ Sync Manager of ADM, which allows authenticated users to copy arbitrary files from the server file system into their own EZSync folder. The vulnerability is due to a lack of authorization checks on the file parameter of the HTTP request. Attackers can exploit this flaw to access files outside their authorized scope, provided the file has readable permissions for other users on the underlying OS. This can lead to unauthorized exposure of sensitive data.
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.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2025-7699 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-7699 is a high-severity missing authorization vulnerability in ASUSTOR ADM, published on 16 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-7699 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-7699/ (Markdown: https://insights.sbomify.com/CVE-2025-7699/index.md)
```

## Sources

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

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