Security readout for executives and security teams
Plain-English summary
Affected Windows versions of the Final Fantasy XIV launcher could expose login credentials if a user was on a network controlled or intercepted by an attacker. The issue came from loading a script over HTTP before using HTTPS. Sources say Square Enix fixed it in Patch 4.3.
Executive priority
Treat this as a targeted endpoint hygiene issue, not a broad infrastructure emergency. Prioritize if the organization permits games on managed devices or has unmanaged endpoints accessing corporate networks.
Technical view
ffxivlauncher.exe in Final Fantasy XIV 4.21 and 4.25 for Windows retrieved global.js over HTTP before proceeding with HTTPS. That weak channel integrity created a man-in-the-middle credential-theft risk. The source bundle identifies Patch 4.3 as the fix.
Likely exposure
Exposure is limited to Windows systems running the affected Final Fantasy XIV launcher versions 4.21 or 4.25. Enterprise exposure is most plausible on BYOD, shared workstations, or unmanaged endpoints where the game client is installed.
Exploitation context
The provided sources describe a man-in-the-middle attack path but do not cite public exploitation, mass exploitation, or CISA KEV listing. Exploitation would require attacker positioning on the user’s network path or equivalent traffic interception capability.
Researcher notes
The record lacks CVSS, CWE, and structured CPE data, so product matching depends on the textual description. Sources consistently identify Final Fantasy XIV 4.21 and 4.25 on Windows and state the issue was fixed in Patch 4.3.
Mitigation direction
- Apply Final Fantasy XIV Patch 4.3, identified as the fix.
- Remove or replace launcher versions 4.21 and 4.25 on Windows systems.
- Restrict use on untrusted networks until affected launchers are updated.
- Check current Square Enix guidance before relying on alternate mitigations.
Validation and detection
- Inventory Windows endpoints for ffxivlauncher.exe and affected game versions.
- Confirm affected installations have Patch 4.3 applied.
- Review network controls for historical HTTP retrieval of global.js by the launcher.
- Verify unmanaged or BYOD endpoints are covered by software inventory policy.
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-2018-7295 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://raw.githubusercontent.com/WizardShotTheFood/advisories/master/CVE-2018-7295.txtCVE 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.