dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-10544

HIGH · 8.6 CVSS v4.0 Published 2025-09-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
92/100
Remediation priority · Urgent
Remotely reachable 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
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.

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

Unrestricted file upload vulnerability in AvePoint's DocAve, Perimeter, and Compliance Guardian platforms allows authenticated administrator users to upload files without proper validation. Combined with path traversal, attackers can write malicious files to arbitrary directories within the web root, potentially achieving remote code execution.

MitigationImplement strict allowlist-based file type validation, sanitize file names to prevent path traversal, store uploaded files outside the web root, and disable script execution in upload directories.

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
Low
Privileges
High
Authentication
X
User interaction
None
Scope
X

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/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. Identify AvePoint products installed
    Check system inventory or installed programs for DocAve, Perimeter, or Compliance Guardian. Look in Program Files for AvePoint directories, or check IIS/web server for AvePoint web applications.
    Affected if Any of the three affected products (DocAve, Perimeter, Compliance Guardian) are installed on the server
  2. Verify administrator access exists
    Check if any administrator-level user accounts exist in the AvePoint platform's user database or Active Directory integration. Look for accounts with Admin or Platform Administrator roles.
    Affected if Authenticated administrator users are present in the AvePoint environment
  3. Confirm file upload functionality is enabled
    Locate the file upload module in the web interface or configuration. Check if upload endpoints exist under the DocAve/Perimeter/Compliance Guardian web paths (e.g., /upload, /FileUpload, or similar). Review web.config or application settings for upload-enabled modules.
    Affected if File upload functionality is accessible to authenticated administrators
  4. Check for path traversal protections in upload handlers
    Review the file upload handler code or configuration. Examine upload validation logic for proper filename sanitization. Look for lack of ../ sequences being blocked in upload parameters.
    Affected if Upload handler lacks path traversal sanitization or allows .. sequences in filenames
  5. Inspect web root for suspicious uploaded files
    Search web root directories (inetpub/wwwroot or equivalent) for recently created files with extensions like .asp, .aspx, .php, .jsp, .exe, or .js that do not match legitimate upload sources.
    Affected if Unexpected script or executable files exist in web-accessible directories

The environment is affected if any AvePoint product is installed AND authenticated administrator access exists AND file upload without path traversal validation is enabled.

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

Implement strict allowlist-based file type validation, sanitize file names to prevent path traversal, store uploaded files outside the web root, and disable script execution in upload directories.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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