Security readout for executives and security teams
Plain-English summary
This issue affects Yellowfin Smart Reporting versions described as before 7.3, with 7.4 and later listed as fixed. A victim could be lured to an attacker-controlled site, causing browser-based abuse of Yellowfin admin functionality without the victim realizing it.
Executive priority
Treat this as a targeted application-risk item, not a confirmed emergency. Upgrade or retire affected Yellowfin deployments because the described impact involves admin-function access through a victim browser, but available severity data is incomplete.
Technical view
The CVE describes an incorrect access control privilege-escalation issue involving MIAdminStyles.i4 and an XSS-style attack path on the target domain. The available record lacks CVSS, CWE detail, and vendor advisory context, so technical scope and preconditions remain incomplete.
Likely exposure
Exposure is likely limited to organizations running Yellowfin Smart Reporting versions covered by the CVE record. The bundle names versions before 7.3 and says 7.4 and later are fixed; status of 7.3 is unclear from the provided sources.
Exploitation context
The source describes social engineering to lure a victim to an attacker-controlled site, then silent browser-based exploitation. There is no KEV listing and no provided source showing active exploitation in the wild.
Researcher notes
The public record is sparse. It identifies the product, affected range, component, attack pattern, and fixed version, but omits CVSS, CWE, detailed prerequisites, proof status, and vendor remediation notes beyond 7.4+.
Mitigation direction
- Inventory Yellowfin Smart Reporting deployments and record exact versions.
- Prioritize upgrade planning to Yellowfin Smart Reporting 7.4 or later.
- Check Yellowfin vendor guidance for version-specific upgrade and hardening instructions.
- Limit administrative access to trusted networks and named administrators.
- Review browser and application session controls for privileged Yellowfin users.
Validation and detection
- Confirm whether any Yellowfin Smart Reporting instance is below the fixed version.
- Verify the MIAdminStyles.i4 component is not exposed on vulnerable deployments.
- Review access logs for unexpected administrative actions by legitimate users.
- Confirm administrative users have least-privilege roles.
- Document whether compensating controls reduce browser-based attack exposure.
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-1010147 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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 and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://drive.google.com/open?id=1sk5IklziyEggeWpWE4Wyk9xqa30CjNpSCVE reference · x_refsource_MISC
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.