CVE-2025-15149
Cross-Site Scripting in rawchen ecms Add New Product Page
Publication date: 2025-12-28
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| rawchen | ecms | * |
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. |
| CWE-94 | The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the updateProductServlet function of the Add New Product Page component in rawchen ecms. It involves the manipulation of the productName argument, which leads to a cross-site scripting (XSS) vulnerability. This means an attacker can inject malicious scripts remotely, potentially affecting users who interact with this component.
How can this vulnerability impact me? :
The vulnerability allows remote attackers to perform cross-site scripting attacks by manipulating the productName argument. This can lead to the execution of malicious scripts in the context of users' browsers, potentially resulting in unauthorized actions, data theft, or session hijacking. However, the CVSS scores indicate a low to moderate impact, with no confidentiality or availability impact but some integrity impact.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'productName' parameter in the 'updateProductServlet' interface for improper input sanitization leading to stored cross-site scripting (XSS). You can attempt to inject typical XSS payloads (e.g., <script>alert(1)</script>) into the 'productName' field and observe if the script executes when the stored data is accessed. Since the vulnerability requires authentication, detection should be performed with valid credentials. Network detection might involve monitoring HTTP requests to the updateProductServlet endpoint for suspicious payloads in the 'productName' parameter. Specific commands are not provided in the resources. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include avoiding use of the affected product or replacing it, as no official patches or countermeasures have been released. Additionally, restrict access to the vulnerable 'updateProductServlet' interface to trusted users only, enforce strict input validation and sanitization on the 'productName' parameter if possible, and monitor for suspicious activity. Since the vendor has not provided a fix, consider implementing web application firewalls (WAF) rules to detect and block XSS payloads targeting this parameter. [1]