Planning Analytics vulnerabilitiesAnd the versions its exploited flaws hit.
Planning Analytics is made by IBM. We track 28 published vulnerabilities listed under that exact name, across 9 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 3 November 2021. IBM lists newer releases under their own names, such as Planning Analytics Local, so check those pages too.
The most recent Planning Analytics flaw added to the known-exploited list is CVE-2019-4716, on 3 November 2021. We keep watching the known-exploited list.
Is Planning Analytics listed under other names? Yes.
IBM also lists Planning Analytics under more specific names, such as Planning Analytics Local and Planning Analytics Workspace. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which versions of Planning Analytics do the exploited flaws hit?
Each exploited flaw lists the versions it affects, as published by the vendor. Find your version, then patch.
- CVE-2019-4716Exploited list, 3 Nov 2021
IBM Planning Analytics Remote Code Execution Vulnerability
2.0 to 2.0.8
Which Planning Analytics vulnerabilities are being exploited?
1 flaw is on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.
- 9.8IBM Planning Analytics Remote Code Execution Vulnerability
IBM Planning Analytics is vulnerable to a configuration overwrite that allows an unauthenticated user to login as "admin", and then execute code as root or SYSTEM via TM1 scripting.
Which Planning Analytics flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 86%
IBM Planning Analytics 2.0.0 through 2.0.8 is vulnerable to a configuration overwrite that allows an unauthenticated user to login as "admin", and then execute code as root or SYSTEM via TM1 scripting.
- 1.8%CVE-2021-38873High
IBM Planning Analytics 2.0 is potentially vulnerable to CSV Injection.
- 1.3%CVE-2020-4527Medium
IBM Planning Analytics 2.0 could allow a remote attacker to obtain sensitive information, caused by the failure to set the Secure flag for the session cookie in TLS mode.
- 1.3%CVE-2020-4562Medium
IBM Planning Analytics 2.0 could allow a remote attacker to obtain sensitive information by allowing cross-window communication with unrestricted target origin via documentation frames.
- 1.2%CVE-2020-4953Medium
IBM Planning Analytics 2.0 could allow a remote authenticated attacker to obtain information about an organization's internal structure by exposing sensitive information in HTTP repsonses.
- 1.1%CVE-2021-20526Medium
IBM Planning Analytics 2.0 could allow a remote attacker to obtain sensitive information, caused by the failure to set the HTTPOnly flag.
- 1.1%CVE-2023-42017Critical
IBM Planning Analytics Local 2.0 could allow a remote attacker to upload arbitrary files, caused by the improper validation of file extensions.
- 1.1%CVE-2021-29851Medium
IBM Planning Analytics 2.0 could allow a remote attacker to obtain sensitive information when a stack trace is returned in the browser.
- 1.0%CVE-2020-4873Medium
IBM Planning Analytics 2.0 could allow an attacker to obtain sensitive information due to an overly permissive CORS policy.
- 1.0%CVE-2020-4361Medium
IBM Planning Analytics 2.0 could allow a remote attacker to obtain sensitive information by disclosing private IP addresses in HTTP responses.
Running Planning Analytics? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 flaw being exploited affects software Acme tracks
IBM Planning Analytics is vulnerable to a configuration overwrite that allows an unauthenticated user to login as "admin", and then execute code as root or SYSTEM via TM1 scripting.
- Matched to
- Planning Analytics on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 28 published vulnerabilities listed under the name Planning Analytics, across 9 versions. The most recent Planning Analytics flaw added to the known-exploited list is CVE-2019-4716, on 3 November 2021.
1 is on the list of flaws known to be exploited. The most recently added is CVE-2019-4716.
IBM also lists Planning Analytics under more specific names, such as Planning Analytics Local and Planning Analytics Workspace. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Each flaw names its own versions, usually as ranges. The newest, CVE-2019-4716, affects 2.0 to 2.0.8. The versions for every exploited flaw are listed on this page.
Create a EdgeProtect account and track Planning Analytics. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.