Skip to main content
Vulnerability Database/CVE-2025-22244

CVE-2025-22244: Broadcom VMware NSX Stored XSS Vulnerability

CVE-2025-22244 is a stored cross-site scripting flaw in Broadcom VMware NSX gateway firewall caused by improper input validation. Attackers can inject malicious scripts to compromise user sessions and data. This article covers technical details, affected versions, security impact, and recommended mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2025-22244 Overview

CVE-2025-22244 is a stored Cross-Site Scripting (XSS) vulnerability affecting VMware NSX and related Broadcom products. The flaw resides in the gateway firewall component and stems from improper input validation [CWE-79]. An authenticated attacker with high privileges can inject malicious script payloads that persist in the NSX management interface. When another administrator views the affected content, the payload executes in their browser session.

Critical Impact

An attacker can inject persistent script payloads into the NSX gateway firewall interface, enabling session manipulation and administrative actions against higher-privileged users who view the stored content.

Affected Products

  • Broadcom VMware NSX (including version 4.2.2)
  • VMware Cloud Foundation
  • VMware Telco Cloud Infrastructure
  • VMware Telco Cloud Platform

Discovery Timeline

  • 2025-06-04 - CVE-2025-22244 published to the National Vulnerability Database
  • 2025-06-04 - Broadcom publishes Security Advisory #25738
  • 2026-06-17 - Last updated in NVD database

Technical Details for CVE-2025-22244

Vulnerability Analysis

The vulnerability is a stored Cross-Site Scripting (XSS) issue classified under CWE-79. The NSX gateway firewall component fails to properly validate or sanitize user-supplied input before storing it. The input is later rendered in the administrative interface without adequate output encoding.

When a victim administrator loads the affected view, the browser interprets the injected content as executable script. The scope-changed impact means code executes within the context of the NSX management UI, potentially crossing trust boundaries. Attackers can leverage this to perform actions on behalf of the victim, modify firewall rules, or exfiltrate session data.

Exploitation requires high privileges on the NSX appliance and user interaction from a second administrator. These prerequisites reduce opportunistic exploitation but do not eliminate risk in environments with multiple administrators or shared tenancy models.

Root Cause

The root cause is improper neutralization of input during web page generation. The gateway firewall configuration fields accept characters that should be encoded or stripped before persistence. Rendering routines then output the stored data without context-aware encoding, allowing script tags and event handlers to execute in the victim's browser.

Attack Vector

The attack vector is network-based and remote. An authenticated attacker with firewall configuration privileges submits a crafted payload through NSX firewall rule fields or related configuration elements. The payload is stored server-side. A privileged administrator later navigates to a view that renders the stored data, triggering script execution in their authenticated session.

No verified public exploit code is available. The vulnerability mechanism is described in prose per the Broadcom Security Advisory #25738.

Detection Methods for CVE-2025-22244

Indicators of Compromise

  • Unexpected <script> tags, HTML event handlers, or encoded JavaScript strings within NSX gateway firewall rule names, descriptions, or tag fields.
  • Audit log entries showing firewall configuration changes made by administrators that correlate with anomalous browser-driven API calls.
  • Session artifacts indicating actions performed from an administrator's browser without corresponding user intent (unexpected rule changes, user additions, or policy modifications).

Detection Strategies

  • Query NSX configuration exports and search for HTML or JavaScript syntax inside firewall object fields, descriptions, and tags.
  • Review NSX Manager audit logs for configuration changes submitted by authenticated users with elevated roles immediately preceding administrator UI access.
  • Deploy browser-side Content Security Policy monitoring on NSX management workstations to flag inline script execution attempts.

Monitoring Recommendations

  • Centralize NSX Manager syslog and API audit events into a SIEM for correlation of configuration writes and administrative sessions.
  • Alert on firewall object creation or modification containing suspicious character sequences such as <script, onerror=, javascript:, or base64-encoded payloads.
  • Monitor administrator session activity for API calls originating from the management UI that fall outside normal administrative workflows.

How to Mitigate CVE-2025-22244

Immediate Actions Required

  • Apply the fixed versions identified in Broadcom Security Advisory #25738 across all NSX, Cloud Foundation, Telco Cloud Infrastructure, and Telco Cloud Platform deployments.
  • Audit existing NSX gateway firewall objects for stored script payloads and remove any suspicious content before administrators access those views.
  • Review and reduce the number of accounts with high-privilege firewall configuration rights to limit the pool of potential attackers.

Patch Information

Broadcom has released patches addressing CVE-2025-22244. Refer to Broadcom Security Advisory #25738 for the complete list of fixed versions corresponding to each affected product line. Administrators should prioritize patching NSX Manager instances exposed to multiple administrative users.

Workarounds

  • Restrict access to NSX gateway firewall configuration to a minimal set of trusted administrators until patches are deployed.
  • Enforce separation of duties so that administrators who create firewall objects differ from those who review them, reducing XSS payload delivery opportunities.
  • Access the NSX management UI from dedicated, hardened administrative workstations with strict browser security policies to limit script execution impact.
bash
# Review NSX firewall objects for potential XSS payloads via the NSX Policy API
curl -k -u 'admin:<password>' \
  -H 'Accept: application/json' \
  https://<nsx-manager>/policy/api/v1/infra/domains/default/gateway-policies \
  | grep -Ei '<script|onerror=|javascript:|onload='

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.