WebdatorcentralApplication · Kabona Ab

CVE-2016-8376

MEDIUM · 6.1 CVSS v3.0 Published 2017-02-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
An issue was discovered in Kabona AB WebDatorCentral (WDC) application prior to Version 3.4.0. This non-validated redirect/non-validated forward (OPEN REDIRECT) allows chaining with authenticated vulnerabilities.

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 confidence

WebDatorCentral (WDC) versions prior to 3.4.0 contain an open redirect vulnerability where the application fails to properly validate redirect or forward parameters, allowing attackers to craft malicious URLs that redirect users to arbitrary external sites. This vulnerability can be chained with authenticated vulnerabilities for more impactful attacks.

MitigationUpgrade to WebDatorCentral version 3.4.0 or later which contains the fix for the unvalidated redirect/forward vulnerability.

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
WebdatorcentralApplication
Affected:all versions

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
High
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:N/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 checks

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

  1. Identify WebDatorCentral version
    Locate the installation directory and check version file, or access the application help/about page. Common paths include the web root or configuration files. Alternatively, check HTTP response headers or application login page footer for version information.
    Affected if The installed version is any version prior to 3.4.0, or if version information cannot be determined but the product is confirmed as WebDatorCentral
  2. Confirm application is running and accessible
    Access the WebDatorCentral web interface via HTTP/HTTPS to verify the application is deployed. Attempt to reach the login page or main entry point.
    Affected if The application is accessible online, making the redirect functionality exploitable
  3. Inspect redirect parameter in authentication flow
    Examine the login page URL and HTML source for redirect or forward parameters (commonly named 'redirect', 'url', 'next', 'target', or 'return_url'). Check form action URLs and any query string parameters that control post-login destination.
    Affected if A redirect or forward parameter exists in the authentication flow that accepts arbitrary URLs without validation
  4. Test redirect parameter behavior
    Observe what happens when a crafted URL with an external domain in the redirect parameter is used (for example, redirect=https://example.com). Do not follow the redirect, only observe if the application accepts and processes the external URL.
    Affected if The application accepts and processes an external domain in the redirect parameter without sanitization or rejection

A user is affected if WebDatorCentral version is confirmed below 3.4.0 or unknown, and the application exposes a redirect parameter that accepts arbitrary external URLs without validation.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to WebDatorCentral version 3.4.0 or later which contains the fix for the unvalidated redirect/forward vulnerability.

Fix this in Webdatorcentral Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-8376 — 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-2016-8376 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