BackupApplication · Msp360

CVE-2025-43595

CRITICAL · 9.8 CVSS v3.1 Published 2025-05-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/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
An insecure file system permissions vulnerability in MSP360 Backup 4.3.1.115 allows a low privileged user to execute commands with root privileges in the 'Online Backup' folder. Upgrade to MSP360 Backup 4.4 (released on 2025-04-22).

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

MSP360 Backup version 4.3.1.115 contains insecure file system permissions in the 'Online Backup' folder that allows a low-privileged local user to escalate privileges to root by manipulating files or executing malicious code within that folder.

MitigationUpgrade MSP360 Backup to version 4.4 or later to resolve the file permission vulnerability.

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
BackupApplication
Affected:= 4.3.1.115

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 MSP360 Backup installation
    Check for MSP360 Backup installation directory (typically C:\Program Files\MSP360\Backup or C:\Program Files (x86)\MSP360\Backup) or look in Add/Remove Programs for MSP360 Backup.
    Affected if MSP360 Backup version 4.3.1.115 is installed.
  2. Confirm installed version
    Locate the MSP360 Backup executable (usually Backup.exe) in the installation folder, right-click, select Properties, and check the File version on the Details tab.
    Affected if The version shown is exactly 4.3.1.115.
  3. Locate the Online Backup folder
    Search for a folder named 'Online Backup' within the MSP360 installation directory or in common data directories such as C:\Users\Public\Documents\MSP360\ or the user's AppData folder.
    Affected if The 'Online Backup' folder exists on the system.
  4. Inspect folder permissions
    Right-click the 'Online Backup' folder, select Properties, go to the Security tab, and examine which users and groups have permissions. Focus on whether low-privileged users (especially Everyone, Users, or authenticated users) have Write or Modify permissions.
    Affected if Low-privileged local users have Write, Modify, or Full Control permissions to the folder.

A system is affected if MSP360 Backup version 4.3.1.115 is installed AND the 'Online Backup' folder grants write/modify permissions to non-admin users.

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

Upgrade MSP360 Backup to version 4.4 or later to resolve the file permission vulnerability.

Recommended fix High confidence

MSP360 Backup 4.4

  1. 1. Download MSP360 Backup version 4.4 from the official vendor source (help.msp360.com or official download渠道)
  2. 2. Create a complete backup of current configuration and data
  3. 3. Stop the MSP360 Backup service if running
  4. 4. Install or upgrade to MSP360 Backup 4.4
  5. 5. Verify the installation completed successfully
  6. 6. Start the MSP360 Backup service
  7. 7. Confirm the file permissions in the 'Online Backup' folder are now correct and no longer allow low-privileged users to execute commands with elevated privileges

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

Fix this in Backup Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-43595 — 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-43595 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