dbcve.org
Planning AnalyticsApplication · Ibm

CVE-2018-1933

MEDIUM · 5.4 CVSS v3.0 Published 2019-05-01
Fix available
A fix is available. Upgrade to after 2.0.6 or later.
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 Planning Analytics 2.0 through 2.0.6 is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 153177.

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

IBM Planning Analytics versions 2.0 through 2.0.6 contains a cross-site scripting (XSS) vulnerability in its Web UI. Attackers can inject arbitrary JavaScript code through the interface, potentially altering application functionality and exposing credentials within trusted user sessions.

MitigationUpgrade IBM Planning Analytics to a version beyond 2.0.6 or apply IBM's subsequent security patches. Implement output encoding and input validation for all user-supplied data in the web interface as a defense-in-depth measure.

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 AnalyticsApplication
Affected:>= 2.0, <= 2.0.6

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.0/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 IBM Planning Analytics installed version
    Check the installed version through the IBM Planning Analytics administration console, or inspect the installation metadata file (typically found in the installation directory or via the 'tm1top' or 'TM1AdminServer' interface). On Windows, you can also check Add/Remove Programs for the version entry.
    Affected if The installed version is 2.0.x where x is 0 through 6 (i.e., versions 2.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4, 2.0.5, or 2.0.6).
  2. Confirm Web UI component is accessible
    Verify that the IBM Planning Analytics Web interface (TM1 Web or Planning Analytics Workspace) is deployed and accessible. Check if port 9510 (default TM1 Web) or the Planning Analytics Workspace web portal is responding.
    Affected if The Web UI component is exposed and reachable over the network, making it a potential vector for XSS attacks.
  3. Review web server logs for XSS indicators
    Examine IBM Planning Analytics web server logs (typically located in the 'logs' or 'TM1WebLog' directory under the installation path) for suspicious patterns such as <script> tags, javascript:, or other HTML/script injection attempts in URL parameters.
    Affected if Log entries contain unsanitized user input with script tags or XSS payloads that were not properly filtered or encoded.
  4. Inspect browser security reports
    Check any browser-based security reports, Content Security Policy (CSP) violation logs, or user-reported issues that indicate script injection occurring within the Planning Analytics session.
    Affected if Users have reported or logs show unexpected script execution, altered interface behavior, or credential exposure consistent with XSS exploitation.

You are affected if your installed IBM Planning Analytics version falls within 2.0 through 2.0.6 and the Web UI component is accessible to users or attackers.

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
Upgrade available Upgrade to a release after 2.0.6
Interim mitigation

Upgrade IBM Planning Analytics to a version beyond 2.0.6 or apply IBM's subsequent security patches. Implement output encoding and input validation for all user-supplied data in the web interface as a defense-in-depth measure.

Fix this in Planning Analytics Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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