CVE-2026-129541 in EdgeChatinfo

Summary

by MITRE • 11/16/2026

EdgeChat 2.5.0 through 2.21.0 contains a cross-site scripting vulnerability that allows invited users to inject HTML through unescaped usernames in the Vditor @-mention autocomplete. Attackers can register with a username containing an img onerror payload that executes when mentioned, stealing the localStorage session token to take over victim accounts.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Analysis

by VulDB Data Team • 11/16/2026

The security flaw identified in EdgeChat versions 2.5.0 through 2.21.0 represents a significant risk to application integrity and user data confidentiality due to its cross-site scripting nature. This vulnerability specifically targets the Vditor @-mention autocomplete feature, which is designed to facilitate communication by allowing users to reference others within chat messages. The core technical deficiency lies in the improper handling of input validation for usernames during this specific interaction flow. When a user attempts to mention another participant, the system retrieves the username and inserts it into the DOM without adequate sanitization or encoding. This lack of output encoding allows an attacker to inject malicious HTML content directly into the page context when their name is selected from the autocomplete suggestions.

The exploitation vector for this vulnerability relies on social engineering combined with account registration. An adversary can register a new user account using a username that contains a crafted payload, such as an img tag with an onerror event handler designed to execute arbitrary JavaScript code. This setup requires no prior authentication or elevated privileges beyond basic access to the application's public-facing interface. Once the maliciously named account is established, the attacker must wait for a victim user to interact with the chat feature and trigger the @-mention autocomplete function that includes the attacker's username in the suggestion list. When the victim clicks on this suggestion to insert it into their message draft, the browser parses the unescaped HTML content embedded within the username field.

Upon execution of the injected script, the payload leverages the context of the victim's active session to exfiltrate sensitive data. Specifically, the malicious code accesses the localStorage object stored in the user's browser and retrieves the session token or authentication cookie associated with their current login state. This action effectively steals the cryptographic credentials that prove the victim's identity to the application server. By capturing this token, the attacker gains the ability to impersonate the legitimate user without needing their password or multi-factor authentication codes. The stolen data is typically transmitted back to a remote server controlled by the adversary via an HTTP request initiated by the script execution.

The operational impact of this vulnerability extends beyond simple session hijacking and encompasses broader security implications for both individual users and organizational infrastructure. Account takeover allows the attacker to read private messages, access shared files, and potentially send malicious content on behalf of the victim, thereby damaging reputations and spreading further threats within the network. From a classification perspective, this flaw aligns with CWE-79, which describes Improper Neutralization of Input During Web Page Generation commonly known as Cross-site Scripting. Furthermore, in terms of tactical mapping to the MITRE ATT&CK framework, this vulnerability facilitates Initial Access through phishing-like interactions and Credential Access via Browser Session Hijacking techniques such as Stealing User Credentials from Local Storage or Cookie Theft.

Mitigation strategies must address both immediate remediation and long-term architectural improvements. The primary technical fix involves implementing strict output encoding for all dynamic content rendered in the browser, particularly within autocomplete widgets that handle user-generated input like usernames. Developers should ensure that special characters are escaped using context-appropriate methods before insertion into the DOM to prevent them from being interpreted as executable code. Additionally, integrating a Content Security Policy with directives such as script-src can provide an additional layer of defense by restricting where scripts can be loaded from and preventing inline script execution unless explicitly allowed through nonces or hashes. Regular security testing including automated static analysis and manual penetration testing focused on input validation flows is recommended to detect similar flaws in other components before they reach production environments.

Responsible

VulnCheck

Reservation

11/16/2026

Disclosure

11/16/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Do you know our Splunk app?

Download it now for free!