CVE-2026-102667 in Joyland
Summary
by MITRE • 10/01/2026
Joyland AI app allows an attacker with shared network access to inject JavaScript into content loaded in WebView. Without user-granted permissions, an attacker could access the clipboard, make arbitrary HTTP requests via the Weex 'stream' module, or access app-internal storage. If the installed app has been granted permissions previously, the attacker can access the entire file system, camera, microphone, and GPS tracking.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Analysis
by VulDB Data Team • 10/01/2026
The Joyland AI application contains a critical security vulnerability stemming from improper configuration of its WebView component, which facilitates cross-site scripting (XSS) attacks when users are connected to shared or untrusted networks. This flaw allows an attacker positioned in the same network segment to inject malicious JavaScript payloads into content loaded within the app's web view environment. The root cause lies in the failure to adequately sanitize user-supplied input and enforce strict Content Security Policies, thereby permitting arbitrary script execution within the context of the application. This type of vulnerability is commonly classified under CWE-79, which addresses improper neutralization of input during web page generation, a standard weakness that undermines the integrity of client-side applications by allowing attackers to manipulate the DOM and execute code with the privileges of the host application rather than as an isolated script.
The operational impact of this vulnerability is severe due to the elevated permissions typically granted to mobile applications for enhanced functionality. Even without explicit user-granted permissions for sensitive features, the injected JavaScript can exploit native bridges or insecure API calls exposed by the Weex framework's stream module to perform arbitrary HTTP requests and access local clipboard data. This capability enables attackers to intercept sensitive information such as authentication tokens, personal messages, or financial details stored in the system clipboard. Furthermore, the ability to make network requests allows for further exploitation vectors, including phishing attacks that mimic legitimate services or exfiltration of application state data to remote servers controlled by the attacker.
If the Joyland AI app has been previously granted broader permissions by the user, such as access to storage, camera, microphone, or location services, the consequences escalate significantly. The injected code can leverage these existing privileges to read files from the entire file system, capture audio and video feeds without consent, and track the physical location of the device owner. This represents a profound breach of privacy and data confidentiality, effectively turning the compromised application into a surveillance tool for the attacker. Such behavior aligns with ATT&CK techniques related to Collection via Clipboard Access (T1056) and Data from Local System (T1005), highlighting how mobile vulnerabilities can be chained to achieve comprehensive device compromise similar to desktop malware infections.
Mitigation strategies must focus on hardening the WebView configuration and enforcing strict security policies. Developers should disable JavaScript execution in WebViews unless absolutely necessary, or if required, implement rigorous input validation and output encoding to prevent script injection. Additionally, enabling Content Security Policy headers with a nonce-based approach can restrict the sources from which scripts are loaded, ensuring that only trusted code executes within the app environment. It is also critical to review and minimize the permissions requested by the application, adhering to the principle of least privilege so that even if an XSS vector is exploited, the attacker cannot access high-risk features like camera or file system unless explicitly justified for core functionality. Regular security audits and static analysis tools should be employed to detect such misconfigurations before deployment to production environments.