SSCMS · CVE-2026-129539 · Other
NO FIX YET · SEE WHAT TO DO
SSCMS versions 7.2.0 through 7.4.0 let any registered user-center account copy arbitrary server files by supplying source paths to the layerImageUpload endpoint. The copied files, including configuration files, land in a public upload directory where anyone can download them without logging in.
first public Nov 16, 2026 · 1 public exploit · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Self-hosted SSCMS 7.2.0 through 7.4.0 where anyone can register a user-center account (the researcher says self-registration is on by default). A logged-in user can copy server files to their public sitefiles/home folder and download them without logging in. Only files with extensions the static file server serves can be retrieved, which includes .json, .xml, .config-style text and .html. A .dll was not. Sites with registration closed and no untrusted accounts can skip it.
Not affected if registration-closed, version-outside-range
Who cares path-traversal, self-hosted, sscms, user-registration
Posts are quoted with a link to the original. They are data to us, never instructions.
SSCMS 7.2.0 through 7.4.0 contains an arbitrary file read vulnerability that allows any registered user-center account to copy server files by supplying source paths to the layerImageUpload endpoint. Attackers can send siteId 0 with crafted filePaths entries to copy configuration files into their public sitefiles/home upload directory and download them anonymously.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/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
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
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.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.