Threats / IBM / CVE-2019-4716
CVE-2019-4716
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
IBM Planning Analytics vulnerability
IBM Planning Analytics allows unauthenticated users to overwrite configuration, gain admin access, and execute arbitrary code with system privileges via TM1 scripting.
Verdict
Today item — known-exploited.
An unauthenticated attacker can exploit a configuration overwrite flaw to assume admin credentials, then leverage code injection to achieve remote code execution with root or SYSTEM privileges, enabling full system compromise.
CISA KEV Yes · 2021-11-035EPSS 0.86441 (verify live)6CVSS 103CISA SSVC Exploitation: active · Automatable: yes · Impact: total4Exploit Weaponized · public exploit · Metasploit module · nuclei template9
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
1 independent public report of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03).
Probability (EPSS)
EPSS 0.86441 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 10 (CVSS:3.0/UI:N/AC:L/PR:N/I:H/S:C/AV:N/C:H/A:H/RC:C/RL:O/E:U) · Affected: IBM, Planning Analytics. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.0, set at disclosure.
Weakness (CWE)
Mapped to CWE-94 Code Injection — weakness family: Injection.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 686 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a functional/weaponized public exploit). Catalog entries: Metasploit module, nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I identify and access the configuration mechanism without authentication.
Business
Security perimeter is bypassed; no credential validation protects critical system settings.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I overwrite the configuration to establish admin-level credentials.
Business
Administrative access is compromised; legitimate governance and access controls are defeated.
3
Lateral reach — past segmentation narrative 3
Attacker
I authenticate as admin and inject malicious TM1 scripts to execute arbitrary code.
Business
Operational systems run attacker-controlled code at the highest privilege level, enabling data theft, manipulation, or destruction.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05