dbcve.org
Db2 Intelligence CenterApplication · Ibm

CVE-2025-14687

MEDIUM · 6.5 CVSS v3.1 Published 2025-12-26
Fix available
A fix is available. Upgrade to 1.1.3 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 Db2 Intelligence Center 1.1.0, 1.1.1, 1.1.2 could allow an authenticated user to perform unauthorized actions due to client-side enforcement of sever side security mechanisms.

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

IBM Db2 Intelligence Center versions 1.1.0 through 1.1.2 contains a broken access control vulnerability where the application relies on client-side enforcement for server-side security decisions. This allows authenticated users to bypass authorization checks by modifying client-side parameters or requests, enabling unauthorized actions within the application.

MitigationImplement robust server-side authorization checks for all sensitive operations and remove reliance on client-side validation. Ensure every request enforces proper access control on the backend regardless of client-side state or user-modified parameters.

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
Db2 Intelligence CenterApplication
Affected:>= 1.1.0, < 1.1.3

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
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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. Check installed version of IBM Db2 Intelligence Center
    Locate the product version information. This is typically accessible through the product's web interface under Help > About, or via command line tools such as 'db2icVersion' or similar utilities shipped with the product. Check installation directories for version manifest files.
    Affected if The installed version cannot be determined or is not visible through standard methods.
  2. Compare version against affected range
    Review the identified version number. The affected range is versions 1.1.0 through 1.1.2 inclusive. Versions prior to 1.1.0 are not affected. Version 1.1.3 and later contain the fix.
    Affected if The installed version is 1.1.0, 1.1.1, or 1.1.2.
  3. Confirm product is in use
    Verify that IBM Db2 Intelligence Center is actively deployed and accessible to users. The vulnerability requires an authenticated user session to exploit, so confirm user accounts exist and the application accepts connections.
    Affected if The product is installed and operational with user authentication enabled.

If IBM Db2 Intelligence Center version is 1.1.0, 1.1.1, or 1.1.2, the environment is affected by this broken access control vulnerability that allows authenticated users to bypass authorization via client-side parameter manipulation.

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
Upgrade available Upgrade to 1.1.3 or later
Fixed in 1.1.3
Interim mitigation

Implement robust server-side authorization checks for all sensitive operations and remove reliance on client-side validation. Ensure every request enforces proper access control on the backend regardless of client-side state or user-modified parameters.

Recommended fix Moderate confidence

IBM Db2 Intelligence Center version 1.1.3

  1. 1. Back up the current IBM Db2 Intelligence Center installation and associated data.
  2. 2. Review IBM Db2 Intelligence Center 1.1.3 release notes for any migration requirements or prerequisites.
  3. 3. Stop all Db2 Intelligence Center services.
  4. 4. Upgrade the installation to version 1.1.3 following IBM's standard upgrade procedures for this product.
  5. 5. Restart services and verify the application is functioning correctly.
  6. 6. Confirm the fix by testing that server-side authorization controls cannot be bypassed via client-side request manipulation.

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

Fix this in Db2 Intelligence Center Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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