dbcve.org
DatacapApplication · Ibm

CVE-2024-39728

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 stored cross-site scripting. This vulnerability allows users 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: 295967.

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 9.1.5-9.1.9 contains a stored cross-site scripting (XSS) vulnerability in its Web UI. Attackers can embed arbitrary JavaScript code into the application, which executes when other users view the affected content, potentially allowing credential theft within trusted sessions.

MitigationApply IBM's available patch or upgrade to a fixed version. Implement output encoding and input validation for all user-supplied data in the Web UI.

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 IBM Datacap version
    Check the installed version of IBM Datacap in your environment using your package manager, installation logs, or version information tool provided by IBM.
    Affected if The installed version is 9.1.5, 9.1.6, 9.1.7, 9.1.8, or 9.1.9.
  2. Identify IBM Datacap Navigator version
    Check the installed version of IBM Datacap Navigator in your environment using your package manager, installation logs, or version information tool provided by IBM.
    Affected if IBM Datacap Navigator is installed at any version.
  3. Confirm Web UI is accessible
    Verify whether the IBM Datacap or Datacap Navigator Web UI is enabled and accessible to users. This is typically accessed via a browser to the application's web endpoint.
    Affected if The Web UI is enabled and users can access it to interact with the application.
  4. Review Web UI input fields
    Inspect the Web UI for input fields that accept user-supplied data and are stored by the application, such as profile fields, document metadata, or configuration entries.
    Affected if User-supplied data can be stored and displayed back to other users without sanitization.

You are affected if IBM Datacap version 9.1.5-9.1.9 or any version of IBM Datacap Navigator is installed and its Web UI is accessible to 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply IBM's available patch or upgrade to a fixed version. Implement output encoding and input validation for all user-supplied data in the Web UI.

Recommended fix Moderate confidence

IBM Datacap 9.1.9 or later

  1. Check IBM's official support portal or IBM Fix Central for the latest IBM Datacap version
  2. Download and install IBM Datacap version 9.1.9 or later which addresses the stored XSS vulnerability
  3. Verify the upgrade by reviewing release notes for CVE-2024-39728 / IBM X-Force ID 295967
  4. After upgrade, test the Web UI to confirm the XSS fix is applied and functionality works as expected
Caveat Review IBM Datacap 9.1.9 release notes for any migration considerations or deprecations before upgrading

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

Fix this in Datacap Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-39728 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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