# CVE-2025-7379: A security bypass vulnerability was found in DataSync Center installed on ADM

> Attackers can exploit Reverse Tabnabbing in DataSync Center to steal credentials and bypass security controls, requiring users to upgrade the application.

- **Severity:** Medium 5.2 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:P/VC:L/VI:L/VA:L/SC:H/SI:H/SA:H`)
- **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:** 9 Jul 2025
- **Updated:** 9 Jul 2025
- **Also known as:** GHSA-g895-c46p-862g

## What is CVE-2025-7379?

CVE-2025-7379 is a medium-severity vulnerability in ASUSTOR ADM, published on 9 Jul 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

A security bypass vulnerability allows exploitation via Reverse Tabnabbing, a type of phishing attack where attackers can manipulate the content of the original tab, leading to credential theft and other security risks. This issue affects DataSync Center: from 1.1.0 before 1.1.0.r207, and from 1.2.0 before 1.2.0.r206.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2025-7379 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-7379 is a medium-severity vulnerability in ASUSTOR ADM, published on 9 Jul 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-7379 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-7379/ (Markdown: https://insights.sbomify.com/CVE-2025-7379/index.md)
```

## Sources

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

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