Cloud FoundationApplication · VMware
CVE-2025-22245
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 contains a stored Cross-Site Scripting (XSS) vulnerability in the router port 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 contains a stored Cross-Site Scripting (XSS) vulnerability in the router port configuration due to improper input validation. Attackers can inject malicious scripts that persist on the server and execute in the browsers of other users accessing the router port interface.
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
- Low
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L
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 NSX product and versionAccess the NSX Manager web interface, navigate to System > Support, or run 'get version' via API to retrieve the installed product name and exact version numberAffected if The version falls within any of these ranges: Cloud Foundation 4.5-5.2.1.2, Telco Cloud Infrastructure 2.2-3.0, Telco Cloud Platform 3.0-5.0, NSX 3.2 to below 4.1.2.6, NSX 4.2.1 to below 4.2.1.4, or exactly 4.2.2
-
Verify router port configuration accessCheck if users with administrative or network admin roles can access the router port configuration UI under Networking > Routers > [Select Router] > Ports, or query the NSX API endpoint for router port resourcesAffected if The router port configuration interface is accessible and users can create or modify router port entries
-
Review existing router port entries for injected contentUse NSX API GET /api/v1/router-ports or navigate the UI to list all router port configurations and inspect the name, description, IP assignment, and tag fields for any unexpected HTML tags, script elements, or encoded charactersAffected if Any router port entry contains raw script tags, onclick handlers, or other JavaScript code in text fields that were not intentionally configured by an administrator
-
Check audit logs for router port modificationsReview NSX Manager audit logs under System > Audit Log, filtering for events involving router-port creation or modification, and look for entries containing suspicious payload patternsAffected if Audit logs show router port modifications containing script tags or unusual character sequences that resemble XSS injection attempts
A user is affected if their NSX product version falls within the affected ranges AND the router port configuration feature is accessible, with any existing router port entries containing injected script content.
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.
From vendor data4.1.2.64.2.1.4
Apply VMware's official patch for NSX when available. Until then, implement output encoding for all router port inputs and restrict administrative access to minimize exposure to authenticated attackers.
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-22245 — 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-22245 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