dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-7379

MEDIUM · 5.2 CVSS v4.0 Published 2025-07-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
56/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

DataSync Center versions 1.1.0 before r207 and 1.2.0 before r206 are vulnerable to Reverse Tabnabbing, where malicious websites can manipulate the original tab's content after a user clicks an external link. This allows attackers to spoof legitimate pages and steal credentials.

MitigationApply vendor patches (1.1.0.r207 or 1.2.0.r206) to add rel='noopener noreferrer' to all external links or nullify window.opener.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
High
Authentication
X
User interaction
P
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate DataSync Center installation
    Search for DataSync Center in your system: check Program Files (Windows), /Applications (macOS), or /opt (Linux). Look for directories named 'DataSync Center' or files with 'datasync' in the name.
    Affected if DataSync Center is not found on the system, it is not affected.
  2. Determine installed version
    Open DataSync Center and navigate to Help > About, or check the application's manifest/config file for the version number. Look for a version string like '1.1.0.rXXX' or '1.2.0.rXXX'.
    Affected if The installed version cannot be determined or is not visible.
  3. Compare version to affected ranges
    If version is 1.1.x, check if the revision number (r) is less than r207. If version is 1.2.x, check if the revision number is less than r206. Versions 1.1.0.r207 and 1.2.0.r206 and later are patched.
    Affected if Version is 1.1.0 before r207, or 1.2.0 before r206.
  4. Verify external link protection (if accessible)
    Inspect the application's web interface or HTML source files. Check external links (links to domains outside your organization) for the 'rel' attribute containing 'noopener' and 'noreferrer'. Example: <a href='external-site.com' rel='noopener noreferrer'>
    Affected if External links lack rel='noopener noreferrer' or rel='noopener' attributes, or window.opener is not nullified in JavaScript.

The environment is affected if DataSync Center version is 1.1.0 before r207 or 1.2.0 before r206, and external links in the application do not have proper rel='noopener noreferrer' attributes.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches (1.1.0.r207 or 1.2.0.r206) to add rel='noopener noreferrer' to all external links or nullify window.opener.

Recommended fix Moderate confidence

DataSync Center 1.1.0.r207 or later (for 1.1.x branch); DataSync Center 1.2.0.r206 or later (for 1.2.x branch)

  1. 1. Access the Asustor NAS administration interface
  2. 2. Navigate to the App Central or Applications section
  3. 3. Locate DataSync Center application
  4. 4. Check the current installed version of DataSync Center
  5. 5. If version is 1.1.0 before r207, upgrade to version 1.1.0.r207 or later
  6. 6. If version is 1.2.0 before r206, upgrade to version 1.2.0.r206 or later
  7. 7. Verify the upgrade was successful and the application functions normally

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-7379 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-7379 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data