dbcve.org
DatacapApplication · Ibm

CVE-2025-36027

MEDIUM · 5.4 CVSS v3.1 Published 2025-06-28
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 9.1.7, 9.1.8, and 9.1.9 could allow a remote attacker to hijack the clicking action of the victim. By persuading a victim to visit a malicious Web site, a remote attacker could exploit this vulnerability to hijack the victim's click actions and possibly launch further attacks against the victim.

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

This is a clickjacking (UI redress) vulnerability in IBM Datacap versions 9.1.7, 9.1.8, and 9.1.9. An attacker can embed the IBM Datacap application in a transparent iframe on a malicious website, overlaying invisible or disguised clickable elements over legitimate UI. When victims click on what they perceive as normal page content, they are actually triggering actions within the IBM Datacap application.

MitigationImplement X-Frame-Options: DENY or SAMEORIGIN HTTP response header, and/or Content Security Policy with frame-ancestors directive to prevent the application from being embedded in iframes on external domains.

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.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 IBM Datacap application version through the product's About section, installation directory, or version file. Compare against affected versions 9.1.7, 9.1.8, and 9.1.9.
    Affected if The installed version is 9.1.7, 9.1.8, or 9.1.9, or the product is IBM Datacap Navigator (any version).
  2. Inspect HTTP response headers for X-Frame-Options
    Use browser developer tools (Network tab), curl -I, or a header scanning tool to capture HTTP responses from the IBM Datacap web interface. Look for the X-Frame-Options header.
    Affected if The X-Frame-Options header is missing, or is set to ALLOW-FROM (which provides no protection), indicating the application can be embedded in iframes.
  3. Inspect Content Security Policy for frame-ancestors
    Capture HTTP responses from the IBM Datacap web interface and examine the Content-Security-Policy header for the frame-ancestors directive.
    Affected if The CSP frame-anchors directive is missing, or does not restrict iframe embedding to trusted domains, allowing external sites to embed the application.
  4. Verify iframe embedding configuration
    Attempt to load the IBM Datacap application URL within an iframe on a test page, or inspect the response headers from an external origin.
    Affected if The application can be successfully embedded in a cross-origin iframe without restrictions, confirming clickjacking exposure.

A user is affected if they run IBM Datacap versions 9.1.7-9.1.9 or any Datacap Navigator version AND the application lacks proper X-Frame-Options or CSP frame-ancestors restrictions, allowing it to be embedded in external iframes.

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

Implement X-Frame-Options: DENY or SAMEORIGIN HTTP response header, and/or Content Security Policy with frame-ancestors directive to prevent the application from being embedded in iframes on external domains.

Fix this in Datacap Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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