Which versions of Sscms are affected by CVE-2026-4542?

Organizations using A vulnerability should be aware of moderate risk from CVE-2026-4542, a path traversal vulnerability rated CVSS 5.4. This could allow unauthorized file access.

Is there a public PoC exploit available for CVE-2026-4542?

Yes, a public proof-of-concept exploit is available for CVE-2026-4542. Prioritise patching immediately. EPSS: 0.0%.

How to fix or mitigate CVE-2026-4542?

Within 30 days: Identify affected systems and apply vendor patches as part of regular patch cycle. Review file handling controls.

Sscms CVE-2026-4542

Q: What is the CVSS score of CVE-2026-4542?

CVE-2026-4542 has a CVSS 4.0 base score of 2.1 (Low). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/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. EPSS exploitation probability: 0.0%.

EUVD-2026-14294 LOW

Path Traversal (CWE-22)

2026-03-22 VulDB

Path Traversal Sscms

2.1

CVSS 4.0 · NVD

Severity by source

NVD PRIMARY

2.1 LOW

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Severity Changed

Apr 29, 2026 - 01:11 NVD

MEDIUM LOW

CVSS changed

Apr 29, 2026 - 01:11 NVD

5.3 (MEDIUM) 2.1 (LOW)

CVSS changed

Apr 18, 2026 - 05:22 NVD

5.4 (MEDIUM) 5.3 (MEDIUM)

PoC Detected

Mar 23, 2026 - 14:31 vuln.today

Public exploit code

EUVD ID Assigned

Mar 22, 2026 - 09:00 euvd

EUVD-2026-14294

Analysis Generated

Mar 22, 2026 - 09:00 vuln.today

CVE Published

Mar 22, 2026 - 08:35 nvd

MEDIUM 5.4

DescriptionCVE.org

A vulnerability has been found in SSCMS 4.7.0. The affected element is an unknown function of the file LayerImageController.Submit.cs of the component layerImage Endpoint. Such manipulation of the argument filePaths leads to path traversal. The attack may be performed from remote. The exploit has been disclosed to the public and may be used. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

AnalysisAI

SSCMS 4.7.0's layerImage endpoint allows authenticated attackers to manipulate the filePaths parameter in LayerImageController.Submit.cs, enabling path traversal attacks that can modify or delete arbitrary files on the server. Public exploit code exists for this vulnerability, and no patch is currently available.

Technical ContextAI

The vulnerability is rooted in CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), a classic path traversal flaw where user-supplied input is not properly validated before being used in file system operations. The affected component is the LayerImageController.Submit.cs file within SSCMS (likely a content management system), specifically in the layerImage endpoint handling. The filePaths parameter is processed without adequate sanitization, allowing attackers to use path traversal sequences (such as '../' or absolute paths) to access files outside the intended directory structure. This occurs in a REST/HTTP endpoint accessible remotely, indicating the web application accepts untrusted file path inputs directly from the client without canonicalization or whitelisting.

RemediationAI

Immediately upgrade SSCMS to the latest patched version released after 4.7.0; consult the official SSCMS repository or security mailing list for the specific patch version number and advisory details. If an immediate upgrade is not feasible, implement input validation on the filePaths parameter by enforcing a whitelist of allowed file names/paths, rejecting any input containing path traversal sequences ('../', absolute paths, or URL-encoded variants), and using file canonicalization functions to ensure the resolved path remains within the intended directory. Additionally, enforce strict access controls ensuring only authorized users can access the layerImage endpoint, consider implementing Web Application Firewall (WAF) rules to detect and block path traversal attempts, and monitor file system access logs for suspicious activity. The public POC reference at https://www.yuque.com/la12138/pa2fpb/vlyutc51eb7vhwaz?singleDoc should be reviewed to understand attack mechanics and validate remediation effectiveness.