CVE-2026-11975
Received Received - Intake
Stored XSS in SimplCommerce via Unsanitized HTML Fields

Publication date: 2026-06-17

Last updated on: 2026-06-17

Assigner: Checkmarx

Description
Stored cross-site scripting (XSS) in NewsItemApiController In SimplCommerce prior to commit 6142d3b5 allows an authenticated administrator to execute arbitrary JavaScript via the ShortContent and FullContent fields, which are stored without HTML sanitization and rendered unencoded via @Html.Raw()
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-17
Last Modified
2026-06-17
Generated
2026-06-17
AI Q&A
2026-06-17
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
simplcommerce simplcommerce to 6142d3b5 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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 Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability is a stored cross-site scripting (XSS) issue in the NewsItemApiController of SimplCommerce versions prior to a specific fix. It allows an authenticated administrator to inject and execute arbitrary JavaScript code via the ShortContent and FullContent fields. These fields were stored without proper HTML sanitization and rendered unencoded using @Html.Raw(), which enables malicious scripts to run in users' browsers.

Impact Analysis

This vulnerability can impact you by allowing an attacker with administrator access to execute arbitrary JavaScript in the context of the web application. This can lead to session hijacking, defacement, theft of sensitive information, or performing actions on behalf of other users. Since the malicious script is stored and rendered to users, it can affect any user who views the compromised content.

Detection Guidance

This vulnerability involves stored cross-site scripting (XSS) in the ShortContent and FullContent fields of NewsItemApiController in SimplCommerce. Detection involves identifying if these fields contain malicious JavaScript code that is stored and rendered unencoded.

To detect this on your system, you can inspect the content of NewsItem entries for suspicious script tags or JavaScript code in the ShortContent and FullContent fields.

Example commands to detect potential XSS payloads in a database (assuming a SQL-based backend) might include:

  • SELECT * FROM NewsItems WHERE ShortContent LIKE '%<script>%';
  • SELECT * FROM NewsItems WHERE FullContent LIKE '%<script>%';

Additionally, monitoring HTTP requests to the NewsItemApiController endpoints for suspicious input containing script tags or unusual HTML content can help detect exploitation attempts.

Mitigation Strategies

The primary mitigation for this vulnerability is to sanitize the ShortContent and FullContent fields before storing them, preventing malicious scripts from being saved and rendered.

According to the provided resources, the SimplCommerce project fixed this issue by integrating the HtmlSanitizer library in the NewsItemApiController. This sanitizes HTML input to remove potentially harmful scripts.

  • Update SimplCommerce to a version that includes commit 6142d3b5 or later, which applies HtmlSanitizer to sanitize user input.
  • If immediate update is not possible, implement input validation and sanitization on the ShortContent and FullContent fields to remove scripts before saving.
  • Restrict access to the NewsItemApiController endpoints to trusted authenticated administrators only.
  • Review and monitor logs for suspicious activity related to content creation or modification.
Compliance Impact

The vulnerability is a stored cross-site scripting (XSS) issue that allows an authenticated administrator to execute arbitrary JavaScript via unsanitized content fields. Such vulnerabilities can lead to unauthorized access, data leakage, or manipulation of sensitive information.

While the provided context does not explicitly mention compliance with standards like GDPR or HIPAA, XSS vulnerabilities generally pose risks to data integrity and confidentiality, which are critical aspects of these regulations.

Therefore, if exploited, this vulnerability could potentially lead to non-compliance with regulations that require protection of personal data and secure handling of information, such as GDPR and HIPAA.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-11975. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart