Security readout for executives and security teams
Plain-English summary
IBM Planning Analytics 2.0 has a medium-severity web interface flaw that can let an authenticated user place JavaScript into the application. If another trusted user interacts with it, the script could change page behavior or expose credentials within that session.
Executive priority
Treat as a scheduled but real remediation item. It is not marked as actively exploited, but it can affect credentials and trusted financial planning workflows if an attacker has user access.
Technical view
The issue is cross-site scripting in IBM Planning Analytics 2.0 Web UI. The CVSS 3.0 score is 5.4, with network attack vector, low privileges required, user interaction required, changed scope, low confidentiality and integrity impact, and no availability impact.
Likely exposure
Exposure is limited to environments running IBM Planning Analytics 2.0, especially where the Web UI is reachable by many internal users or externally accessible authenticated users.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. Exploitation requires access to the Web UI, low privileges, and user interaction, so risk is mainly authenticated session abuse rather than unauthenticated compromise.
Researcher notes
Evidence supports an authenticated, user-interaction XSS in IBM Planning Analytics 2.0. The bundle names IBM X-Force ID 196949 but does not provide exploit details, affected subcomponents, or a specific fixed build in the provided text.
Mitigation direction
- Review IBM advisory for the fixed Planning Analytics 2.0 level and apply vendor guidance.
- Restrict Web UI access to trusted users and networks where operationally possible.
- Review user roles and remove unnecessary low-privilege access.
- Increase monitoring for unexpected Web UI content or credential-related alerts.
Validation and detection
- Inventory IBM Planning Analytics 2.0 deployments and exposed Web UI endpoints.
- Compare installed versions against the IBM advisory and X-Force entry.
- Confirm whether the affected Web UI is reachable from untrusted networks.
- Review logs for suspicious content changes or anomalous authenticated activity.
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-2021-20477 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/I:L/S:C/AC:L/C:L/AV:N/UI:R/PR:L/A:N/RL:O/E:H/RC:C
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/I:L/S:C/AC:L/C:L/AV:N/UI:R/PR:L/A:N/RL:O/E:H/RC:C2.32.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.0 score
5.4MediumVector: CVSS:3.0/I:L/S:C/AC:L/C:L/AV:N/UI:R/PR:L/A:N/RL:O/E:H/RC:C
Source materials
- CVE List V5 sourceCVE List V5
- https://www.ibm.com/support/pages/node/6462331CVE reference · x_refsource_CONFIRM
- ibm-planning-cve202120477-xss (196949)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.
