CVE-2024-28287
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 DOM-based open redirection in the returnUrl parameter of INSTINCT UI Web Client 6.5.0 allows attackers to redirect users to malicious sites via a 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 · moderate confidenceThis is a DOM-based open redirection vulnerability in the INSTINCT UI Web Client version 6.5.0. The returnUrl parameter in the web application does not properly validate or sanitize user-supplied input, allowing attackers to craft malicious URLs that redirect victims to external malicious websites for phishing or malware delivery purposes.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/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 INSTINCT UI Web Client installationLocate the INSTINCT UI Web Client application in your environment and determine its deployment location (web server directory, application inventory, or service listing)Affected if INSTINCT UI Web Client is not found or is a different version than 6.5.0
-
Verify the installed versionCheck the application version information - typically found in the application metadata, about page, or version file within the INSTINCT UI Web Client deploymentAffected if The installed version is exactly 6.5.0
-
Locate the returnUrl parameter handling codeSearch the web application source code or configuration for usage of the returnUrl parameter - typically in login, logout, or redirect handlersAffected if The application contains code that processes a returnUrl parameter and performs redirects based on its value
-
Inspect input validation on returnUrlExamine the redirect logic to determine if returnUrl is validated against a whitelist of allowed domains or restricted to same-origin URLs before being used in a redirect responseAffected if No validation exists, or validation only strips certain patterns without enforcing strict same-domain or whitelist restrictions
You are affected if INSTINCT UI Web Client version 6.5.0 is deployed and the application uses a returnUrl parameter in redirects without strict domain validation.
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 dataImplement strict input validation on the returnUrl parameter to restrict URLs to trusted origins (same-domain or an explicit whitelist). Apply URL sanitization and canonicalization before using the parameter in redirects.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28287 — 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-2024-28287 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