CVE-2026-7429
Reflected XSS in SSCMS via STL Template Processing
Publication date: 2026-04-30
Last updated on: 2026-04-30
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| siteserver | sscms | to 7.4.0 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-7429 is a reflected Cross-Site Scripting (XSS) vulnerability found in SSCMS version 7.4.0, specifically in the STL processing endpoint.
The vulnerability occurs because the /api/stl/actions/dynamic endpoint improperly encodes output, allowing attackers to inject malicious STL template payloads that are decrypted and returned without proper sanitization.
This flaw enables attackers to execute arbitrary JavaScript code in the context of a victim's browser by crafting and sending specially designed payloads.
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to several security risks including session hijacking, where attackers can steal user session tokens to impersonate users.
It can also facilitate phishing attacks by injecting malicious scripts that trick users into revealing sensitive information.
Additionally, attackers may perform unauthorized actions on behalf of users, potentially compromising the integrity and security of the affected system.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
The vulnerability can be detected by monitoring and analyzing requests to the /api/stl/actions/dynamic endpoint for suspicious or malicious STL template payloads that contain executable JavaScript.
Detection involves identifying POST requests with encrypted STL payloads that, when decrypted, include unsanitized JavaScript code.
Since the vulnerability involves reflected cross-site scripting via crafted STL templates, you can use web application security testing tools or intercepting proxies (like Burp Suite) to capture and analyze traffic to this endpoint.
Example commands or approaches include:
- Using curl to send crafted POST requests to /api/stl/actions/dynamic and inspecting the JSON response for injected scripts.
- Using a web proxy tool to intercept and review requests and responses to detect reflected JavaScript code.
- Searching server logs for unusual or suspicious POST requests to the vulnerable endpoint.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the /api/stl/actions/dynamic endpoint to trusted users only, especially limiting administrator privileges.
Ensure that any STL template payloads are properly sanitized and output encoded before being returned in JSON responses to prevent execution of injected JavaScript.
If possible, apply patches or updates provided by SSCMS that address this vulnerability.
Monitor and block suspicious POST requests that attempt to exploit the vulnerability by injecting malicious STL payloads.
Consider disabling or restricting the use of encrypted STL template processing until a secure fix is applied.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability in SSCMS v7.4.0 allows attackers to execute arbitrary JavaScript via reflected cross-site scripting, which can lead to session hijacking, phishing attacks, and unauthorized actions on behalf of users.
Such security issues can impact compliance with common standards and regulations like GDPR and HIPAA because they may result in unauthorized access to personal or sensitive data, compromise user sessions, and enable phishing attacks that violate data protection and privacy requirements.
However, the provided information does not explicitly discuss the direct impact of this vulnerability on compliance with these standards.