CVE
SiteServer SSCMS arbitrary file read in layerImageUpload endpoint
Affects SSCMS 7.2.0 through 7.4.0, where a regular user can copy files from other server directories into their own public directory and retrieve them without authentication.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
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
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. SSCMS versions 7.2.0 through 7.4.0
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.26% · 17th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 20/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
SSCMS, from siteserver, versions 7.2.0 through 7.4.0, has a flaw in its layerImageUpload endpoint. A remote attacker who holds any registered user-center account can use it to copy server files, such as configuration files, into a publicly downloadable folder and then read them without logging in.
Original description
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.
Who should check
Teams running siteserver SSCMS 7.2.0 through 7.4.0 that allow user-center registration and accounts
“Affected versions: 7.2.0 ~ 7.4.0”
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch5/5No patch listed yet
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 27 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
SSCMS versions 7.2.0 through 7.4.0Workaround: The checked facts do not describe a workaround. Until a fix is confirmed, consult the vendor's advisory for any mitigation it recommends.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-129539 (SSCMS 7.2.0 through 7.4.0 Arbitrary File Read via layerImageUpload Endpoint), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-129539 (entry last updated 2026-11-16):
Affected:
- siteserver SSCMS: from 7.2.0, through 7.4.0
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- SSCMS versions 7.2.0 through 7.4.0 (source: https://vul.yulun.ac.cn/20261114/siteserver-cms/)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-129539 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129539 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/siteserver/cms/issues/3909
- https://vul.yulun.ac.cn/20261114/siteserver-cms/
- https://github.com/siteserver/cms/blob/09ab59b9dd422782d9e1fe54f05088645f7c93e7/src/SSCMS.Web/Controllers/Home/Common/Form/LayerImageUploadController.Submit.cs#L114-L130
- https://www.vulncheck.com/advisories/sscms-7.2.0-through-7.4.0-arbitrary-file-read-via-layerimageupload-endpoint
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-129539
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129539"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- siteserver SSCMS
From 7.2.0 · through 7.4.0
Evidence 6
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 4
- Report
- Repository
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129539
Is CVE-2026-129539 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A regular user can copy files from other directories on the server into their own public directory. Those copied files can then be retrieved without authentication, though retrieval is limited by file extension.Source: vul.yulun.ac.cn
Which versions are affected by CVE-2026-129539?
SSCMS: from 7.2.0 through 7.4.0.Source: cve.now feed data
Am I affected, and how do I check?
The affected versions are SSCMS 7.2.0 through 7.4.0, reached through the layerImageUpload endpoint. Compare the installed SSCMS version against that range to check whether a system falls within it.Source: vul.yulun.ac.cn
How do I fix CVE-2026-129539?
The checked facts do not name a fixed version or patch, so no upgrade target can be given here. Check the vendor's advisory for a fix before relying on any version.Source: vul.yulun.ac.cn
What if there's no patch?
The checked facts do not describe a workaround. Until a fix is confirmed, consult the vendor's advisory for any mitigation it recommends.Source: vul.yulun.ac.cn