Cyber Vision CenterApplication · Cisco
CVE-2025-20357
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 Cyber Vision Center could allow an authenticated, remote attacker to conduct cross-site scripting (XSS) attacks against a user of the interface. This vulnerability is due to insufficient validation of user-supplied input by the web-based management interface of an affected system. An attacker could exploit this vulnerability by injecting malicious code into specific pages of the interface. 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. To exploit this vulnerability, the attacker must have valid administrative credentials that allow access to the Reports page. By default, all pre-defined users have this access, as do any custom users that are configured to allow access to the Reports page.
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 stored XSS vulnerability in Cisco Cyber Vision Center's web-based management interface. An authenticated attacker with administrative credentials and access to the Reports page can inject malicious JavaScript code through insufficiently validated user input. When other users view the compromised Reports page, the injected script executes in their browser context, potentially allowing session hijacking or sensitive information access.
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
Cyber Vision CenterApplication
= 5.1.0= 5.2.0CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 installed Cisco Cyber Vision Center versionAccess the web management interface and navigate to Administration > System > About, or use the CLI command 'show version' if available, to retrieve the Center version numberAffected if The installed version is exactly 5.1.0 or exactly 5.2.0
-
Confirm administrative access to Reports pageLog into the web interface with an administrative account and verify access to the Reports section exists in the navigation menuAffected if The Reports page is accessible and active in the web interface for administrative users
-
Inspect Reports page for existing XSS payloadsNavigate to the Reports page as an administrative user and view the source HTML, or check database tables that store report configurations if CLI/database access is available, for suspicious script tags or event handlersAffected if Malicious JavaScript code or encoded payloads are present in report name fields, descriptions, or generated report output
-
Review user session tokens and access logsCheck browser developer tools for active session cookies while on the Reports page, and review Cisco Cyber Vision access logs for unusual JavaScript-related errors or unauthorized session activity originating from the Reports endpointAffected if Session cookies are being transmitted to third-party domains or abnormal session behavior is logged after viewing Reports page content
-
Audit administrative user accountsReview the list of users with administrative privileges in Administration > User Management to identify any unauthorized accounts that may have been created by an attackerAffected if Unexpected administrative accounts exist that were not created by known administrators
A user is affected if their Cisco Cyber Vision Center runs version 5.1.0 or 5.2.0, the Reports page is accessible, and malicious scripts have been injected into report data or unexpected administrative accounts exist.
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 dataApply the vendor patch when available. Until then, restrict administrative access to the Reports page to only trusted users, and monitor for suspicious activity. Implement output encoding and input validation on all user-supplied data rendered in the web interface.
Fix this in Cyber Vision Center
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20357 — 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-20357 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