CVE-2026-4848
Cross-Site Scripting in dameng100 muucmf /admin/extend/list.html
Publication date: 2026-03-26
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 |
|---|---|---|
| dameng100 | muucmf | 1.9.5.20260309 |
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?
CVE-2026-4848 is a Reflected Cross-Site Scripting (XSS) vulnerability found in Muucmf T6 CMS version 1.9.5.20260309. It occurs in the /admin/extend/list.html endpoint through the "name" parameter. The vulnerability arises because the application directly uses user input in the value attribute of an input tag without any filtering or sanitization. This allows a remote attacker to inject malicious JavaScript code that executes in the victim's browser when they access a specially crafted URL.
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to execute arbitrary JavaScript code in the context of your browser session. This can lead to theft of sensitive information, session hijacking, or manipulation of the web page content. Since the attack is remotely exploitable without any privileges and only requires user interaction, it poses a significant security risk.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the /admin/extend/list.html endpoint for reflected cross-site scripting (XSS) via the "name" parameter.
A common method is to send a crafted HTTP request with a malicious script payload in the "name" parameter and observe if the script is executed or reflected in the response without sanitization.
- Use curl or similar tools to send a request like: curl -i "http://<target>/admin/extend/list.html?name=<script>alert(1)</script>"
- Check the HTTP response for the presence of the injected script tag or payload in the HTML content.
- Alternatively, use a web vulnerability scanner that supports XSS detection targeting the specific URL and parameter.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include sanitizing and validating all user inputs, especially the "name" parameter in /admin/extend/list.html, to prevent injection of malicious scripts.
If possible, apply patches or updates provided by the vendor. However, since the vendor did not respond, consider implementing web application firewall (WAF) rules to block or filter malicious payloads targeting this parameter.
Additionally, restrict access to the /admin/extend/list.html endpoint to trusted users or IP addresses to reduce exposure.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability is a reflected Cross-Site Scripting (XSS) issue that allows remote attackers to inject and execute arbitrary JavaScript code in the context of a victim's browser session. This can lead to unauthorized access to sensitive information, session hijacking, or manipulation of data.
Such security weaknesses can negatively impact compliance with common standards and regulations like GDPR and HIPAA, which require protection of personal and sensitive data against unauthorized access and disclosure. Exploitation of this vulnerability could result in breaches of confidentiality and integrity, potentially leading to violations of these regulations.