CVE-2026-65022 in BigFix MCMinfo

Summary

by MITRE • 11/06/2026

The MDM App Catalog / App Store preview does not properly sanitize or encode user-supplied HTML before rendering it.  Injected HTML can be displayed to users who view the preview, which may allow cross-site scripting (XSS) when a user interacts with the crafted content.

Be aware that VulDB is the high quality source for vulnerability data.

Analysis

by VulDB Data Team • 11/06/2026

The vulnerability identified in the MDM App Catalog and App Store preview functionality represents a classic instance of improper input validation leading to Cross-Site Scripting risks. This flaw stems from the application's failure to adequately sanitize or encode HTML entities within user-supplied data before rendering it for display. In enterprise mobile device management environments, administrators often configure catalog entries that include descriptive text, links, or embedded media previews. When these inputs are processed without rigorous encoding mechanisms such as context-aware escaping of special characters like angle brackets, ampersands, and quotes, the browser interprets injected script tags as executable code rather than static content. This lack of sanitization allows an attacker to inject malicious scripts that execute within the security context of the victim user's session when they view the crafted preview.

From a technical perspective, this issue aligns with CWE-79, which classifies Improper Neutralization of Input During Web Page Generation known as Cross-site Scripting. The root cause lies in the web application framework or custom rendering logic used by the MDM solution to generate HTML previews for app listings. Instead of treating user input strictly as data, the system processes it as part of the document structure without applying necessary transformations such as converting less-than and greater-than symbols into their corresponding HTML entities. Consequently, any script embedded within these fields bypasses client-side defenses because the browser executes them natively upon page load or interaction with specific elements like images or hyperlinks contained in the preview pane.

The operational impact of this vulnerability is significant for organizations relying on centralized application distribution and management. An attacker who gains access to create or modify app catalog entries could exploit this flaw to steal sensitive administrative credentials, session cookies, or multi-factor authentication tokens through cookie theft scripts. Furthermore, the malicious code can perform actions on behalf of the victim user without their knowledge, such as modifying configuration settings, installing unauthorized applications, or exfiltrating data from connected devices. Since MDM consoles typically hold high-privilege access to corporate infrastructure, successful exploitation could serve as an initial foothold for broader network compromise, potentially leading to lateral movement and deeper intrusion into protected systems.

Mitigation strategies must focus on implementing robust input validation and output encoding practices at both the application layer and database level. Developers should enforce strict allow-listing of permitted HTML tags and attributes while stripping out all others using established libraries designed specifically for sanitization rather than simple regex replacements which are prone to bypasses. Additionally, deploying Content Security Policy headers can significantly reduce the impact by restricting script execution sources and preventing inline scripts from running even if injected. Regular security audits focusing on web application logic and automated static analysis tools should be integrated into the development lifecycle to detect such encoding deficiencies early before deployment to production environments where they pose immediate risks to enterprise data integrity and confidentiality.

Responsible

HCL

Reservation

07/21/2026

Disclosure

11/06/2026

Moderation

accepted

EPSS

0.00000

KEV

no

Activities

low

Sources

Do you want to use VulDB in your project?

Use the official API to access entries easily!