Security readout for executives and security teams
Plain-English summary
IBM Planning Analytics 2.0 has a web UI cross-site scripting flaw. A logged-in user could place JavaScript into the interface so another trusted user runs it, potentially exposing credentials or changing expected behavior inside a session.
Executive priority
Treat this as a moderate, authenticated web-application risk. It is most urgent where Planning Analytics is broadly accessible or contains sensitive business data, because compromise could occur within trusted user sessions.
Technical view
The CVE describes stored or embedded JavaScript in the IBM Planning Analytics Web UI. CVSS 3.0 is 5.4, with network access, low privileges, user interaction, changed scope, and low confidentiality and integrity impact. Availability impact is not indicated.
Likely exposure
Organizations running IBM Planning Analytics 2.0, especially where many users can create or modify Web UI content. Exposure depends on authenticated user access and whether other users interact with affected UI content.
Exploitation context
The bundle does not show CISA KEV listing or cited active exploitation. The CVSS temporal vector includes high exploit-code maturity, but that is not the same as confirmed real-world exploitation.
Researcher notes
Key constraints are PR:L and UI:R, with scope changed. The source bundle does not provide CWE, exact fixed versions, or detailed attack surface. Do not infer affected products beyond IBM Planning Analytics 2.0.
Mitigation direction
- Review IBM advisory node 1118565 and X-Force 168519 for official remediation.
- Apply IBM-provided fixes or supported upgrade guidance when confirmed applicable.
- Restrict Planning Analytics Web UI access to trusted users only.
- Review roles that can create or modify Web UI content.
- Monitor for suspicious script-like content in user-controlled UI areas.
Validation and detection
- Inventory IBM Planning Analytics deployments and confirm 2.0 exposure.
- Compare installed builds against IBM advisory guidance.
- Verify Web UI content-modification permissions are least privilege.
- Use approved vulnerability scanning or vendor checks where available.
- Review logs and content history for unexpected UI changes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2019-4611 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.4 (3.0)
- Known Exploited
- No
- Published
Vector: CVSS:3.0/C:L/AC:L/A:N/AV:N/PR:L/S:C/I:L/UI:R/RL:O/RC:C/E:H
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.0/C:L/AC:L/A:N/AV:N/PR:L/S:C/I:L/UI:R/RL:O/RC:C/E:H2.32.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.0 score
5.4MediumVector: CVSS:3.0/C:L/AC:L/A:N/AV:N/PR:L/S:C/I:L/UI:R/RL:O/RC:C/E:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.ibm.com/support/pages/node/1118565CVE reference · x_refsource_CONFIRM
- ibm-planning-cve20194611-xss (168519)CVE reference · vdb-entry, x_refsource_XF
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
