Cloud FoundationApplication · VMware
CVE-2025-22243
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 · uneditedVMware NSX Manager UI is vulnerable to a stored Cross-Site Scripting (XSS) attack 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 confidenceVMware NSX Manager UI contains a stored Cross-Site Scripting (XSS) vulnerability where improper input validation allows attackers to inject malicious scripts that are persisted on the server and executed when other users access the affected UI components. This high-severity vulnerability (CVSS 7.5) affects the management interface and could allow session hijacking, credential theft, or malicious actions performed in the context of authenticated users.
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
>= 4.5, <= 5.2.1.2
Telco Cloud InfrastructureApplication
>= 2.2, <= 3.0
Telco Cloud PlatformApplication
>= 3.0, <= 5.0>= 3.2, < 4.1.2.6>= 4.2.1, < 4.2.1.4= 4.2.2CVSS 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
- Low
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed NSX product and versionRun 'nsx-manager-ctl get-version' or access NSX Manager UI, then navigate to System > Support to view the version. For VMware Cloud Foundation, check the SDDC Manager console for version information.Affected if The installed version falls within these ranges: NSX 3.2 to <4.1.2.6, NSX 4.2.1 to <4.2.1.4, NSX 4.2.2, Cloud Foundation 4.5 to 5.2.1.2, Telco Cloud Infrastructure 2.2 to 3.0, or Telco Cloud Platform 3.0 to 5.0
-
Verify NSX Manager UI is accessibleConfirm that the NSX Manager web interface is enabled and reachable. Access https://<nsx-manager-ip>/ and verify the login page loads.Affected if The NSX Manager UI is exposed and accessible to users
-
Review NSX Manager audit logs for XSS indicatorsIn NSX Manager UI, go to System > Support > Audit Logs. Search for entries containing script tags, javascript:, onload, onerror, or other XSS payloads in user input fields.Affected if Audit logs contain entries with suspicious script tags or XSS payloads in UI-related fields
-
Check for persisted malicious scripts in UI configurationsNavigate to NSX Manager UI sections that accept user input, such as Group names, Tag names, Policy descriptions, or Service definitions. Inspect the HTML source or use browser developer tools to check for unescaped script tags in rendered content.Affected if User-supplied fields in the UI display raw HTML or script tags without encoding
-
Inspect browser console for XSS errors when accessing UI componentsLog into the NSX Manager UI as a standard user and navigate through various UI sections. Open browser developer tools (F12) and check the Console tab for script execution errors or warnings.Affected if The console displays script execution errors indicating reflected or stored XSS payloads are being rendered
You are affected if your NSX Manager, Cloud Foundation, Telco Cloud Infrastructure, or Telco Cloud Platform version is within the listed ranges AND the management UI is accessible and being used.
Generated from the published advisory. Verify against your own configuration.
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 · scoped4.1.2.64.2.1.4
Apply VMware's available patches for NSX Manager and implement output encoding and input validation for all user-supplied data in the NSX Manager UI to prevent script execution.
NSX: 4.1.2.6+ / 4.2.1.4+ / 4.3.x; Cloud Foundation: 5.2.1.3+ / 5.3.x; Telco Cloud Infrastructure: 3.0.1+; Telco Cloud Platform: 5.0.1+
- 1. Identify the specific product and version from the affected list (Cloud Foundation, Telco Cloud Infrastructure, Telco Cloud Platform, or VMware NSX)
- 2. Log into the Broadcom Support portal (support.broadcom.com) and navigate to the product-specific download page
- 3. Download the appropriate patched version for your product: For NSX 4.1.x, upgrade to version 4.1.2.6 or later; For NSX 4.2.x, upgrade to version 4.2.1.4 or later; For NSX 4.2.2, upgrade to the latest available patch; For Cloud Foundation, upgrade to 5.2.1.3 or later (or 5.3.x if available); For Telco Cloud Infrastructure, upgrade to 3.0.1 or later; For Telco Cloud Platform, upgrade to 5.0.1 or
- 4. Review the upgrade guide and release notes for your specific product on the Broadcom support portal
- 5. Create a backup of the current configuration as recommended in the upgrade documentation
- 6. Schedule a maintenance window as XSS patches for management interfaces typically require a reboot or service restart
- 7. Perform the upgrade following the product-specific installation or upgrade procedure
- 8. After upgrade, verify the NSX Manager UI is accessible and functioning normally
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Cloud Foundation
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22243 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-22243 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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