DatacapApplication · Ibm

CVE-2024-39735

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
IBM Datacap Navigator 9.1.5, 9.1.6, 9.1.7, 9.1.8, and 9.1.9 is vulnerable to cross-site scripting. This vulnerability allows an authenticated user to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 296002.

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

IBM Datacap Navigator versions 9.1.5-9.1.9 contain a stored cross-site scripting vulnerability in the Web UI. An authenticated attacker can inject arbitrary JavaScript code that executes in other users' browsers within the trusted session context, potentially enabling credential theft or session hijacking.

MitigationApply IBM security patches for this vulnerability. Until patches are available, implement strict input validation, output encoding on all user-supplied data, and consider Content Security Policy (CSP) headers to mitigate XSS execution.

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
DatacapApplication
Affected:= 9.1.5= 9.1.6= 9.1.7= 9.1.8= 9.1.9
Datacap NavigatorApplication
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
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 IBM Datacap version
    Check the Datacap installation directory for version information, or examine the application logs (typically in the 'logs' folder under the Datacap installation path). The version is also visible in the IBM Datacap Navigator login page footer or in the Help > About section of the application.
    Affected if The installed version matches 9.1.5, 9.1.6, 9.1.7, 9.1.8, or 9.1.9.
  2. Confirm IBM Datacap Navigator is deployed
    Verify that the Datacap Navigator web component is installed and running. Check for the presence of the Navigator web application files in the installation directory (typically under 'web' or 'navigator' subfolders), or check if the Navigator web service is running.
    Affected if IBM Datacap Navigator web interface is present in the environment.
  3. Verify Web UI is accessible
    Attempt to access the Datacap Navigator login page via browser or command line (curl) at the expected URL (commonly http://hostname:9080/navigator or similar port configuration).
    Affected if The Datacap Navigator Web UI responds to HTTP requests and is reachable.
  4. Confirm authentication is enabled
    Check the web application configuration files (such as web.xml or configuration properties in the Navigator setup) to verify that authentication mechanisms are configured and active.
    Affected if Authentication is enabled on the Navigator Web UI, which is required for the authenticated attacker to exploit this vulnerability.

The environment is affected if IBM Datacap version 9.1.5-9.1.9 or any version of IBM Datacap Navigator is installed with its Web UI accessible and authentication enabled.

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

Apply IBM security patches for this vulnerability. Until patches are available, implement strict input validation, output encoding on all user-supplied data, and consider Content Security Policy (CSP) headers to mitigate XSS execution.

Fix this in Datacap Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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