dbcve.org
Cloud FoundationApplication · VMware

CVE-2025-22244

MEDIUM · 6.9 CVSS v3.1 Published 2025-06-04
Fix available
A fix is available. Upgrade to 4.1.2.6 / 4.2.1.4 or later.
See remediation →
73/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
VMware NSX contains a stored Cross-Site Scripting (XSS) vulnerability in the gateway firewall due to improper input validation.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

VMware NSX contains a stored Cross-Site Scripting (XSS) vulnerability in the gateway firewall component due to improper input validation. Attackers can inject malicious scripts into gateway firewall configurations that persist and execute when administrators view the affected interface.

MitigationApply VMware's official patch for this vulnerability and implement output encoding for all user-supplied data displayed in the gateway firewall UI.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Cloud FoundationApplication
Affected:>= 4.5, <= 5.2.1.2
Telco Cloud InfrastructureApplication
Affected:>= 2.2, <= 3.0
Telco Cloud PlatformApplication
Affected:>= 3.0, <= 5.0
Vmware NsxApplication
Affected:>= 3.2, < 4.1.2.6>= 4.2.1, < 4.2.1.4= 4.2.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed VMware product
    Log into the NSX Manager UI or CLI and determine which VMware product is deployed (NSX, Cloud Foundation, Telco Cloud Infrastructure, or Telco Cloud Platform)
    Affected if The product is one of the affected variants listed in the CVE
  2. Determine the product version
    Use the product's admin interface or CLI command (such as 'get version' or 'show version') to retrieve the exact installed version number
    Affected if The version falls within any of the affected ranges: Cloud Foundation 4.5 through 5.2.1.2, Telco Cloud Infrastructure 2.2 through 3.0, Telco Cloud Platform 3.0 through 5.0, or NSX versions 3.2 through 4.1.2.6, 4.2.1 through 4.2.1.4, or exactly 4.2.2
  3. Verify gateway firewall is configured
    Navigate to the gateway firewall section in the NSX Manager UI or use the API endpoint to list gateway firewall policies and rules
    Affected if Gateway firewall policies or rules have been created, as this is the component where the XSS payload would be stored
  4. Inspect gateway firewall configurations for injected scripts
    Review all gateway firewall rule names, descriptions, and rule parameters for suspicious content such as <script> tags, javascript: URIs, or other HTML/script injection patterns
    Affected if Any gateway firewall configuration contains raw script tags, event handlers, or encoded script payloads that could execute when viewed in the admin interface

A user is affected if they are running any of the listed product versions AND have gateway firewall rules configured that contain malicious script content injected by an attacker.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.1.2.6 / 4.2.1.4 or later
Fixed in 4.1.2.64.2.1.4
Interim mitigation

Apply VMware's official patch for this vulnerability and implement output encoding for all user-supplied data displayed in the gateway firewall UI.

Recommended fix High confidence

NSX: 4.1.2.6 (or later 4.1.x), 4.2.1.4 (or later 4.2.1.x), or 4.2.3+ (for 4.2.2); Cloud Foundation 5.2.1.3+; Telco Cloud Infrastructure 3.0.1+; Telco Cloud Platform 5.0.1+

  1. 1. Identify the current NSX deployment version by navigating to System > System Overview in the NSX Manager UI
  2. 2. Determine the appropriate upgrade path based on current version (3.x → 4.1.2.6+, 4.2.1.x → 4.2.1.4+, or 4.2.2 → 4.2.3+)
  3. 3. Review NSX upgrade documentation and release notes for the target version
  4. 4. Create a backup of the NSX configuration
  5. 5. Schedule a maintenance window for the upgrade
  6. 6. Follow VMware/Broadcom upgrade procedures to upgrade NSX to the fixed version: 4.1.2.6 or later for 3.x branches; 4.2.1.4 or later for 4.2.1.x; or 4.2.3 or later for 4.2.2
  7. 7. After upgrade, verify the NSX Manager UI is accessible and the gateway firewall configuration is intact
  8. 8. Validate that the XSS vulnerability is remediated by confirming proper input sanitization in gateway firewall rules
Caveat Review NSX release notes for each upgrade path as there may be compatibility considerations with existing configurations and dependent products

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cloud Foundation Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,260
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,816.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-22244 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-22244 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data