Active Backup For BusinessApplication · Synology

CVE-2025-30028

HIGH · 8.6 CVSS v3.1 Published 2026-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 vulnerability in Active Backup for Business allows unauthorized remote attackers to read arbitrary files.

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 · high confidence

A path traversal vulnerability in Synology Active Backup for Business allows unauthenticated remote attackers to read arbitrary files on the NAS device. The vulnerability is network-exploitable with low complexity and no user interaction required, enabling exfiltration of sensitive configuration files, credentials, or data stored on the affected system.

MitigationApply the vendor patch from Synology when available. Until then, restrict network access to the Active Backup for Business service using firewall rules or network segmentation to limit exposure to trusted internal networks only.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Active Backup For BusinessApplication
Affected:= 2.7.1-23234= 2.7.1-13234= 2.7.1-3234

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
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

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. Verify Active Backup for Business is installed
    Open Synology Package Center and look for 'Active Backup for Business' in the installed packages list, or run 'pkginfo | grep -i active-backup' via SSH on the NAS
    Affected if The package is installed and running on the system
  2. Check the installed version number
    In Synology Package Center, click on Active Backup for Business and view the version details, or run 'pkginfo -l ActiveBackupforBusiness' via SSH to retrieve the exact version string
    Affected if The version matches 2.7.1-23234, 2.7.1-13234, or 2.7.1-3234 exactly
  3. Confirm the service is network-accessible
    Check if the Synology NAS is reachable on the network and that Active Backup for Business ports are open. Use 'netstat -an | grep -E "(port|service)"' or review the NAS firewall rules to determine if the service is exposed to untrusted networks
    Affected if The service port is open to network interfaces accessible from untrusted networks (not restricted to localhost or trusted VLAN)
  4. Verify the web interface is accessible remotely
    Attempt to access the Active Backup for Business web portal from an external network or check if the web service port (typically 30000-30099 range) is listening on external interfaces using 'netstat -tulpn'
    Affected if The web portal responds to requests from untrusted network segments

If Active Backup for Business is installed with version 2.7.1-23234, 2.7.1-13234, or 2.7.1-3234 AND the service is network-accessible, the environment is vulnerable to unauthenticated path traversal attacks.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch from Synology when available. Until then, restrict network access to the Active Backup for Business service using firewall rules or network segmentation to limit exposure to trusted internal networks only.

Fix this in Active Backup For Business Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-30028 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