# CVE-2025-10544: Unrestricted uploading of dangerous file types to AvePoint products

> Administrators can upload malicious files due to lack of validation, potentially leading to system compromise via arbitrary file writes.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Sep 2025
- **Updated:** 26 Sep 2025
- **Also known as:** GHSA-6wwx-2f48-jxh8

## What is CVE-2025-10544?

CVE-2025-10544 is a high-severity vulnerability in AvePoint Compliance Guardian, published on 26 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Unrestricted file upload vulnerability in DocAve 6.13.2, Perimeter 1.12.3, Compliance Guardian 4.7.1, and earlier versions, allowing administrator users to upload files without proper validation. An attacker could exploit this vulnerability by uploading malicious files that compromise the system. In addition, it is vulnerable to Path Traversal, which allows files to be written to arbitrary directories within the web root.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

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

## Is CVE-2025-10544 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10544 is a high-severity vulnerability in AvePoint Compliance Guardian, published on 26 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-10544 in the wild and no public exploit code.

Affected product: AvePoint Compliance Guardian. 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-10544/ (Markdown: https://insights.sbomify.com/CVE-2025-10544/index.md)
```

## Sources

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

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