# CVE-2025-43595: MSP360 Backup (for Linux) insecure filesystem permissions

> A low-privileged user can execute commands with root privileges due to insecure file permissions in the Online Backup folder.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 May 2025
- **Updated:** 22 May 2025
- **Also known as:** GHSA-gjwx-g2ph-472r

## What is CVE-2025-43595?

CVE-2025-43595 is a high-severity vulnerability in MSP360 Backup, published on 1 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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).

Weakness: CWE-276 (Incorrect Default Permissions)

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

It affects 1 product.


Products: Msp360 Backup.

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

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

## Is CVE-2025-43595 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-43595 exists.

## Other vulnerabilities in MSP360 Backup

- [CVE-2025-43596](https://insights.sbomify.com/CVE-2025-43596/): MSP360 Backup (for Windows) insecure filesystem permissions (high 8.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-43595 is a high-severity vulnerability in MSP360 Backup, published on 1 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-43595 exists.

Affected product: MSP360 Backup. 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-43595/ (Markdown: https://insights.sbomify.com/CVE-2025-43595/index.md)
```

## Sources

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

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