Catalyst CenterApplication · Cisco
CVE-2025-20353
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 · uneditedA vulnerability in the web-based management interface of Cisco Catalyst Center could allow an unauthenticated, remote attacker to conduct a cross-site scripting (XSS) attack against a user of the interface of an affected device. This vulnerability is due to insufficient validation of user input. An attacker could exploit this vulnerability by persuading a user of the web-based management interface to click a crafted link. A successful exploit could allow the attacker to execute arbitrary script code in the context of the affected interface or access sensitive, browser-based information.
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 · high confidenceThis is a cross-site scripting (XSS) vulnerability in Cisco Catalyst Center's web-based management interface. An unauthenticated remote attacker can inject malicious script through insufficiently validated user input, which executes when a user clicks a crafted link. The attack runs in the context of the affected interface, potentially exposing sensitive browser-based information.
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
Catalyst CenterApplication
< 2.3.7.10CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Cisco Catalyst Center versionAccess the web-based management interface and locate the version information typically found in the Help > About section, or use the CLI command 'show version' on the appliance if you have administrative accessAffected if The displayed version is lower than 2.3.7.10 (for example, 2.3.7.9, 2.3.7.0, 2.3.6.x, or earlier releases)
-
Confirm web management interface is activeVerify that the Cisco Catalyst Center web-based management interface is reachable and functional by accessing the login page via HTTPS on the configured management IP or hostnameAffected if The web interface is accessible and responding to HTTP/HTTPS requests, indicating the attack surface exists
You are affected if your Cisco Catalyst Center version is below 2.3.7.10 and the web-based management interface is accessible to network users.
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 · scoped2.3.7.10
Apply the Cisco patch when available; until then, train users to avoid clicking untrusted links and consider WAF rules to detect XSS attack patterns.
Cisco Catalyst Center version 2.3.7.10 or later
- 1. Review Cisco Catalyst Center upgrade documentation and release notes for version 2.3.7.10
- 2. Ensure proper backups of current configuration and data are in place
- 3. Verify hardware requirements and compatibility for the upgrade
- 4. Download Cisco Catalyst Center version 2.3.7.10 or later from Cisco.com
- 5. Schedule maintenance window as upgrades require downtime
- 6. Execute upgrade following Cisco's documented upgrade procedure
- 7. After upgrade, verify the Catalyst Center web interface is accessible and functioning properly
- 8. Confirm the XSS vulnerability is remediated by testing that user input is properly validated
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Catalyst Center
Scoped from the published advisory
- Consultation4.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,440.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20353 — 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-20353 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