LiveActive security incident?Get immediate response
CVE Record

CVE-2018-1933: IBM Planning Analytics 2.0 through 2.0.6 is vulnerable to cross-site scripting.

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.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

IBM Planning Analytics 2.0 through 2.0.6 has a cross-site scripting flaw in its Web UI. A user could place JavaScript into the interface, changing what another trusted session sees or does and potentially exposing credentials. This is a moderate business risk when affected systems are used by multiple users or handle sensitive planning data. Exposure is limited to IBM Planning Analytics deployments running versions 2.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4, 2.0.5, or 2.0.6. Systems with broad authenticated user access to the Web UI have higher practical risk. Prioritize remediation during the next planned security maintenance window, faster if the Web UI is widely accessible or used with sensitive finance credentials. The issue is not critical, but credential exposure inside trusted sessions can create downstream business risk. Mitigation focus: Identify all IBM Planning Analytics instances and versions.; Apply IBM vendor guidance from the official advisory.; Upgrade or remediate any 2.0 through 2.0.6 deployments..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2018-1933 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AC:L/S:C/I:L/PR:L/A:N/C:L/UI:R/AV:N/RC:C/E:H/RL:O

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.0MediumCVSS:3.0/AC:L/S:C/I:L/PR:L/A:N/C:L/UI:R/AV:N/RC:C/E:H/RL:O2.32.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

5.4Medium
CVSS 3.0 vector shape for CVE-2018-1933Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AC:L/S:C/I:L/PR:L/A:N/C:L/UI:R/AV:N/RC:C/E:H/RL:O

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
IBMPlanning Analytics2.0.3, 2.0, 2.0.1, 2.0.2, 2.0.4, 2.0.5, 2.0.6Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.