Video InsightApplication · I Pro

CVE-2023-40535

MEDIUM · 5.4 CVSS v3.1 Published 2023-09-05
Fix available
A fix is available. Upgrade to 7.9.6 or later.
See remediation →
58/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
Stored cross-site scripting vulnerability in View setting page of VI Web Client prior to 7.9.6 allows a remote authenticated attacker to inject an arbitrary script.

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 confidence

A stored cross-site scripting vulnerability exists in the View settings page of VI Web Client versions prior to 7.9.6. An authenticated attacker can inject malicious JavaScript code that gets stored in the application and executes in the browsers of other users who access the View settings page.

MitigationUpgrade VI Web Client to version 7.9.6 or later. Until upgraded, restrict access to authenticated users only and implement output encoding on user-supplied data displayed in the View settings page.

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
Video InsightApplication
Affected:< 7.9.6

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
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 checks

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

  1. Identify installed VI Web Client version
    Locate the version information for I Pro Video Insight (VI Web Client) in the application's about page, admin panel, or installation directory. Common locations include the web interface footer, a version info file, or the software's system information page.
    Affected if Version is below 7.9.6
  2. Verify View settings page accessibility
    Navigate to the View settings page in the VI Web Client interface. This is typically found in the administration or configuration section of the web client.
    Affected if The View settings page loads and is accessible to authenticated users
  3. Confirm authentication requirements for the affected page
    Check the access control configuration for the VI Web Client and specifically the View settings page to determine what level of authentication is required.
    Affected if Authenticated users can access the View settings page (the vulnerability requires an authenticated attacker to inject the payload)

Your environment is affected if VI Web Client (I Pro Video Insight) is installed at a version lower than 7.9.6 and the View settings page is accessible to authenticated users.

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 7.9.6 or later
Fixed in 7.9.6
Interim mitigation

Upgrade VI Web Client to version 7.9.6 or later. Until upgraded, restrict access to authenticated users only and implement output encoding on user-supplied data displayed in the View settings page.

Recommended fix High confidence

Video Insight 7.9.6 or later

  1. Identify the current Video Insight VI Web Client version currently deployed
  2. Back up all Video Insight configurations, databases, and important data before proceeding with the upgrade
  3. Download Video Insight version 7.9.6 or later from the official vendor download source (downloadvi.com or authorized channel)
  4. Install or apply the upgrade following the vendor's documented upgrade procedure
  5. Verify the installed version shows 7.9.6 or later after completing the upgrade
  6. Test the View setting page in the VI Web Client to confirm the application functions correctly and the XSS vulnerability is remediated

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

Fix this in Video Insight Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-40535 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-40535 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