CVE-2023-38574
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 · uneditedOpen redirect vulnerability in VI Web Client prior to 7.9.6 allows a remote unauthenticated attacker to redirect users to arbitrary web sites and conduct phishing attacks via a specially crafted URL.
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 an open redirect vulnerability in VI Web Client where the application fails to properly validate redirect URLs before forwarding users. A remote unauthenticated attacker can craft a malicious URL containing a redirect parameter pointing to an external attacker-controlled domain, causing legitimate users to be unknowingly redirected to phishing or malicious sites while believing they remain on the trusted VI Web Client domain.
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< 7.9.6CVSS 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 if I Pro Video Insight is installedLocate the VI Web Client installation directory or check installed programs list for 'I Pro Video Insight' or 'VI Web Client' softwareAffected if The software is present on the system
-
Determine the installed versionCheck the software version through the application itself, its about dialog, or installation metadata files in the program directoryAffected if The installed version number is less than 7.9.6
-
Verify the web client interface is accessibleConfirm the VI Web Client web interface is running and reachable on the network (typically via HTTP/HTTPS on configured ports)Affected if The web interface is exposed and the software version is below 7.9.6
-
Test redirect parameter validationCraft a test URL with a redirect parameter pointing to an unrelated domain (for example: https://your-vi-web-client-url/login?redirect=https://example.com) and observe whether the application allows the redirect without validation or blocks itAffected if The application redirects to the external domain without validating the redirect URL or presenting a warning confirmation page
You are affected if I Pro Video Insight (VI Web Client) is installed with a version lower than 7.9.6 AND the web interface is accessible, allowing unvalidated external redirects via URL parameters.
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 · scoped7.9.6
Upgrade VI Web Client to version 7.9.6 or later to obtain the fix for this open redirect vulnerability.
7.9.6
- Verify current Video Insight installation version through the VI Web Client or system administration panel
- Download Video Insight version 7.9.6 from the official vendor source (downloadvi.com)
- Back up the current Video Insight configuration and database following vendor backup procedures
- Install version 7.9.6 using the vendor's standard upgrade process
- Verify the upgrade was successful by checking the VI Web Client version information
- Test that the application functions normally after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-38574 — 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-2023-38574 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