Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-14806: CWE-524 Use of Cache Containing Sensitive Information in IBM Planning Analytics Local

0
Medium
VulnerabilityCVE-2025-14806cvecve-2025-14806cwe-524
Published: Tue Mar 17 2026 (03/17/2026, 21:50:21 UTC)
Source: CVE Database V5
Vendor/Project: IBM
Product: Planning Analytics Local

Description

CVE-2025-14806 is a medium severity vulnerability in IBM Planning Analytics Local versions 2. 1. 0 through 2. 1. 17. It involves improper caching behavior where sensitive, user-specific data can be stored and served as publicly cacheable resources. An attacker with limited privileges and requiring user interaction can exploit this to access confidential information. The vulnerability does not impact system integrity or availability but poses a significant confidentiality risk. No known exploits are currently reported in the wild. Organizations using affected IBM Planning Analytics Local versions should prioritize patching or implementing mitigations to prevent unauthorized data exposure.

AI-Powered Analysis

AILast updated: 03/17/2026, 22:28:24 UTC

Technical Analysis

CVE-2025-14806 is a vulnerability identified in IBM Planning Analytics Local versions 2.1.0 through 2.1.17, categorized under CWE-524, which concerns the use of caches containing sensitive information. The flaw arises from the caching mechanism improperly handling user-specific responses, causing them to be stored and served as publicly cacheable resources. This misconfiguration allows an attacker to trick the system into exposing sensitive data intended for individual users to other unauthorized users. The vulnerability requires network access (AV:N), low attack complexity (AC:L), and privileges (PR:L), along with user interaction (UI:R). The scope is unchanged (S:U), and the impact primarily affects confidentiality (C:H) without affecting integrity or availability. This means that while the system's data or operations are not altered or disrupted, sensitive information leakage can occur, potentially exposing confidential business analytics data. No patches are currently linked, and no exploits have been reported in the wild, indicating that the vulnerability might be newly disclosed or not yet actively exploited. The vulnerability is significant in environments where sensitive financial or operational data is processed and cached, as unauthorized access to this data could lead to information disclosure and compliance violations.

Potential Impact

The primary impact of CVE-2025-14806 is the unauthorized disclosure of sensitive, user-specific information due to improper caching. Organizations relying on IBM Planning Analytics Local for critical business intelligence and financial analytics could face confidentiality breaches, potentially exposing proprietary or personal data. This leakage could undermine trust, violate data protection regulations such as GDPR or HIPAA, and lead to reputational damage. Although the vulnerability does not affect system integrity or availability, the exposure of sensitive data can facilitate further attacks, including social engineering or targeted phishing. The requirement for privileges and user interaction somewhat limits exploitation but does not eliminate risk, especially in environments with many users or where attackers can trick users into interacting with malicious content. The absence of known exploits suggests a window for proactive mitigation before widespread abuse occurs.

Mitigation Recommendations

To mitigate CVE-2025-14806, organizations should first verify if they are running affected versions (2.1.0 through 2.1.17) of IBM Planning Analytics Local and plan to upgrade to a patched version once available. In the absence of an official patch, administrators should review and harden caching configurations to ensure sensitive user-specific data is never stored in publicly accessible caches. This may include disabling caching for authenticated user responses or implementing cache-control headers that prevent public caching (e.g., 'Cache-Control: private, no-store'). Additionally, network segmentation and strict access controls should be enforced to limit exposure to trusted users only. Monitoring and logging access to cached resources can help detect anomalous access patterns. Educating users about phishing and social engineering risks can reduce the likelihood of successful exploitation requiring user interaction. Finally, coordinate with IBM support for updates and guidance on secure configuration best practices.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
ibm
Date Reserved
2025-12-16T22:13:03.714Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69b9d201771bdb1749dc568a

Added to database: 3/17/2026, 10:13:21 PM

Last enriched: 3/17/2026, 10:28:24 PM

Last updated: 3/18/2026, 5:20:50 AM

Views: 6

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses