VulnerabilityPublished 26 Mar 2026

CVE-2026-4847: dameng100 muucmf · Cross-site Scripting

Affects dameng100 muucmfSource CVE Database V5

Public exploit available · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
dameng100muucmf	Affected =1.9.5.20260309	Fixed in–

AI-suggested

Implement strict input validation and output encoding on the 'Name' parameter in /admin/config/list.html to neutralize malicious script content.
Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers.
Restrict access to the administrative interface by IP whitelisting or VPN to reduce exposure to untrusted networks.
Educate users, especially administrators, about the risks of clicking on suspicious links or interacting with untrusted content.
Monitor web server logs and application behavior for unusual requests targeting the vulnerable parameter.
If possible, upgrade to a patched version once the vendor releases one or consider alternative software solutions.
Use web application firewalls (WAF) with custom rules to detect and block XSS payloads targeting this vulnerability.
Regularly back up configuration and data to enable recovery in case of compromise.
Isolate administrative interfaces from public internet access where feasible.
Conduct security assessments and penetration testing focused on input validation weaknesses in the application.

Description

A vulnerability was found in dameng100 muucmf 1.9.5.20260309. The impacted element is an unknown function of the file /admin/config/list.html. Performing a manipulation of the argument Name results in cross site scripting. The attack can be initiated remotely. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The primary impact of CVE-2026-4847 is the compromise of user session confidentiality and integrity through the execution of arbitrary scripts in the victim’s browser. Attackers can leverage this to steal session cookies, perform unauthorized actions on behalf of the user, deface web content, or redirect users to malicious websites. Since the vulnerability is in an administrative interface, successful exploitation could lead to elevated risks if administrators are targeted, potentially resulting in broader system compromise. The lack of authentication requirement lowers the barrier for attackers, but user interaction is necessary, which may limit automated mass exploitation. The public availability of exploit code increases the risk of opportunistic attacks. Organizations relying on dameng100 muucmf 1.9.5.20260309 may face reputational damage, data breaches, and operational disruptions if this vulnerability is exploited. The absence of vendor response and patches prolongs exposure, necessitating immediate mitigation efforts by affected parties.

Summary

CVE-2026-4847 is a cross-site scripting vulnerability identified in dameng100 muucmf version 1.9.5.20260309. The vulnerability resides in an unspecified function within the /admin/config/list.html file, where the 'Name' parameter is improperly sanitized, allowing attackers to inject malicious JavaScript code. This injection occurs when the parameter is manipulated remotely, without requiring authentication, and the attack requires user interaction to trigger the malicious script execution. The vulnerability is classified as medium severity with a CVSS 4.0 base score of 5.3, reflecting its network attack vector, low attack complexity, no privileges required, and user interaction needed. The impact primarily affects the confidentiality and integrity of user sessions by enabling script execution in the victim’s browser context, which can lead to session hijacking, unauthorized actions, or phishing. The vendor was notified early but has not issued any response or patch, and no official remediation is available. The public disclosure of exploit code increases the likelihood of exploitation attempts, although no active exploitation has been confirmed. This vulnerability highlights the importance of proper input validation and output encoding in web applications, especially in administrative interfaces.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Mar 2026, 18:34 UTC

Technical details

References

Community reviews

Related threats