dbcve.org
Planning Analytics LocalApplication · Ibm

CVE-2025-14806

MEDIUM · 5.7 CVSS v3.1 Published 2026-03-17
Fix available
A fix is available. Upgrade to 2.1.18 or later.
See remediation →
61/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 Planning Analytics Local 2.1.0 through 2.1.17 could allow an attacker to trick the caching mechanism into storing and serving sensitive, user-specific responses as publicly cacheable resources.

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 Planning Analytics Local versions 2.1.0 through 2.1.17 contains a cache poisoning vulnerability where the caching mechanism can be tricked into storing and serving sensitive, user-specific responses as publicly cacheable resources, potentially allowing unauthorized access to confidential data.

MitigationFix the caching mechanism to properly distinguish between public and user-specific responses, ensuring sensitive responses are not cached as publicly accessible content or use appropriate cache-control headers.

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
Planning Analytics LocalApplication
Affected:>= 2.1.0, < 2.1.18

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/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 Planning Analytics Local version
    Check the product version through the TM1 Web interface, the IBM Planning Analytics administration console, or by querying the tm1srv.ini configuration file typically located in the installation directory.
    Affected if The installed version is 2.1.0 through 2.1.17 inclusive.
  2. Locate the TM1 server configuration files
    Navigate to the IBM Planning Analytics Local installation directory and examine the tm1srv.ini or tm1s.cfg file for caching-related configuration parameters.
    Affected if Caching is enabled in the configuration and sensitive endpoints are configured to be cached.
  3. Inspect HTTP response headers for cache-control directives
    Use browser developer tools or a command-line tool like curl to capture HTTP responses from the Planning Analytics web interface. Examine the Cache-Control and Vary headers.
    Affected if Responses containing sensitive user-specific data return cacheable directives (such as 'public' or missing 'no-store') without proper Vary headers to distinguish user context.
  4. Review custom TM1 REST API applications
    Examine any custom applications or integrations that use the TM1 REST API to retrieve user-specific data. Check if these applications explicitly set cache-control headers.
    Affected if Custom applications retrieve sensitive data without setting appropriate cache-control headers to prevent public caching.
  5. Check proxy or load balancer caching configuration
    If IBM Planning Analytics Local is deployed behind a reverse proxy or load balancer, review the proxy configuration for caching rules that may cache sensitive user responses.
    Affected if The proxy is configured to cache responses from Planning Analytics without proper differentiation between public and user-specific content.

A user is affected if their installed IBM Planning Analytics Local version is between 2.1.0 and 2.1.17 and the caching mechanism is configured to store user-specific sensitive responses as publicly cacheable content.

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 2.1.18 or later
Fixed in 2.1.18
Interim mitigation

Fix the caching mechanism to properly distinguish between public and user-specific responses, ensuring sensitive responses are not cached as publicly accessible content or use appropriate cache-control headers.

Recommended fix Moderate confidence

2.1.18

  1. Back up current IBM Planning Analytics Local installation and databases
  2. Download IBM Planning Analytics Local version 2.1.18 from IBM Fix Central or your authorized IBM distribution channel
  3. Follow IBM's standard upgrade procedure for Planning Analytics Local (typically running the installer on the existing installation directory)
  4. Restart Planning Analytics services after upgrade completes
  5. Verify the upgrade was successful by checking the version number in the Planning Analytics administration interface

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

Fix this in Planning Analytics Local Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing5.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,150
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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