CVE-2025-36357
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 · uneditedIBM Planning Analytics Local 2.1.0 through 2.1.14 could allow a remote authenticated user to traverse directories on the system. An attacker could send a specially crafted URL request containing absolute path sequences to view, read, or write arbitrary files on the system.
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 confidenceIBM Planning Analytics Local versions 2.1.0 through 2.1.14 contains a path traversal vulnerability that allows authenticated remote users to access arbitrary files on the host system via specially crafted URL requests containing absolute path sequences (e.g., ../../). This could enable attackers to read sensitive configuration files, credentials, or other system files, or potentially write files depending on the application's file handling functionality.
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>= 2.1.0, < 2.1.15>= 2.1.0, < 2.1.15CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed version of IBM Planning Analytics LocalCheck the product version through the administration interface or by reviewing the installation documentation for your deployment. On Windows, this is often visible in Add/Remove Programs or the TM1Web installation directory. On Linux, check the installed package or the version file in the installation directory.Affected if The installed version is 2.1.0 through 2.1.14 (any version >= 2.1.0 but < 2.1.15)
-
Identify installed version of IBM Planning Analytics WorkspaceCheck the Workspace version through the administration console or by reviewing the installation documentation. This is typically accessible via the IBM Planning Analytics Workspace web interface or the installation logs.Affected if The installed version is 2.1.0 through 2.1.14 (any version >= 2.1.0 but < 2.1.15)
-
Verify if remote access to TM1Web or Workspace is enabledReview the web server configuration files (such as web.config for IIS or the IBM TM1 web configuration) to determine if TM1Web or Planning Analytics Workspace is exposed for remote HTTP/HTTPS connections.Affected if The web interface is accessible remotely and the server is network-exposed
-
Check for presence of authentication on Planning Analytics endpointsReview the authentication configuration in the IBM Planning Analytics administration settings to confirm whether user authentication is required for accessing TM1Web or Workspace URLs.Affected if Authentication is disabled or optional, allowing unauthenticated access
-
Review web server access logs for path traversal patternsExamine TM1Web or Planning Analytics Workspace access logs (typically found in the logs directory of the installation) for requests containing ../, ..\, or absolute path sequences such as /../../
You are affected if either IBM Planning Analytics Local or Workspace is installed at version 2.1.0 through 2.1.14, the web interface is accessible, and authentication can be bypassed or is exploitable.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.1.15
Upgrade to IBM Planning Analytics Local version 2.1.15 or later, which addresses this vulnerability. If immediate upgrading is not feasible, implement strict input validation to reject URLs containing path traversal sequences (../, absolute paths) and restrict file access permissions to minimize exposure.
IBM Planning Analytics Local and Workspace version 2.1.15
- 1. Back up all existing IBM Planning Analytics Local and Workspace data, configurations, and databases before proceeding with the upgrade.
- 2. Download IBM Planning Analytics version 2.1.15 (or later) from IBM Fix Central or your authorized IBM distribution channel.
- 3. Upgrade IBM Planning Analytics Local to version 2.1.15 or later by following the IBM Installation and Configuration Guide for your platform.
- 4. Upgrade IBM Planning Analytics Workspace to version 2.1.15 or later using the same upgrade procedures.
- 5. After upgrading both components, restart all Planning Analytics services to ensure the new version loads correctly.
- 6. Verify the upgrade was successful by logging into Planning Analytics Workspace and confirming normal functionality.
- 7. Validate that the path traversal vulnerability is remediated by ensuring absolute path sequences in URLs are no longer accepted by the application.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36357 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-36357 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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