CVE-2026-123973 · Other
NO FIX YET · SEE WHAT TO DO
CopyMove for SharePoint 2019 and CopyMove for SharePoint V6 have a path traversal flaw in their ZIP import feature. An authenticated user with access to that feature can supply a crafted ZIP archive whose entry paths write files outside the intended extraction directory.
first public Nov 6, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Organizations running CopyMove for SharePoint 2019 or CopyMove for SharePoint V6 where users can use the ZIP import feature. Exposure depends on the add-on being installed and on which accounts hold ZIP import permission. Farms without the add-on, or where only trusted administrators can use ZIP import, are lower risk.
Not affected if add-on-not-installed, no-zip-import-access
Who cares copymove-for-sharepoint, self-hosted, sharepoint
SharePoint Products CopyMove before 2026-11-06 allows traversal. An authenticated SharePoint user with the necessary permissions to use the ZIP import functionality may exploit a path traversal vulnerability in CopyMove for SharePoint 2019 and CopyMove for SharePoint V6 by supplying a crafted ZIP archive. A path traversal vulnerability in the ZIP import functionality of SharePoint Products ApS CopyMove for SharePoint 2019 and CopyMove for SharePoint V6 allows a user with access to the ZIP import functionality to supply a crafted ZIP archive containing malicious entry paths. During extraction, these paths may cause files to be written outside the intended extraction directory. The issue has been addressed by implementing ZIP archive entry path validation to prevent extraction outside the designated directory.
This page as .md · .json · CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.