A filename spoofing vulnerability exists in WinRAR when opening specially crafted ZIP archives. The issue arises due to inconsistencies between the Central Directory and Local File Header entries in ZIP files. When viewed in WinRAR, the file name from the Central Directory is displayed to the user, while the file from the Local File Header is extracted and executed. An attacker can leverage this flaw to spoof filenames and trick users into executing malicious payloads under the guise of harmless files, potentially leading to remote code execution.
Security readout for executives and security teams
Plain-English summary
A crafted ZIP can show a harmless-looking filename in WinRAR while extracting and launching a different embedded file. The business risk is malware execution after a user opens and trusts an archive. Public exploit material exists, but the provided sources do not show confirmed active exploitation.
Executive priority
Treat this as a high-priority hygiene issue where legacy WinRAR remains installed. The weakness depends on user interaction, but public exploit material and plausible phishing delivery make it relevant for endpoint risk reduction.
Technical view
The flaw comes from inconsistent ZIP Central Directory and Local File Header filenames. WinRAR displays one name but extracts and executes the other, enabling filename spoofing and potential code execution with user action. The supplied record rates it CVSS 8.4 and maps it to CWE-20 and CWE-434.
Likely exposure
Exposure is most likely on Windows endpoints using old WinRAR versions named in the record, including 3.80 and 4.11, especially where users open untrusted ZIP attachments or downloads. The title says WinRAR before 5.00, but the supplied affected list is narrower.
Exploitation context
The sources include public technical and exploit references, including a Metasploit module, so proof-of-concept capability is public. KEV is false in the bundle, and no cited source in the bundle confirms active exploitation in the wild.
Researcher notes
Do not infer current exploitation from exploit availability alone. The key research focus is confirming exact vulnerable versions from RARLab and CVE data, then validating whether endpoint controls detect misleading archive extraction and execution behavior.
Mitigation direction
Inventory WinRAR installations and identify versions matching the supplied affected record.
Update WinRAR according to RARLab vendor guidance or replace unsupported versions.
Block or quarantine untrusted ZIP archives from email and web download paths where feasible.
Educate users not to execute files from unexpected archives, even if names appear harmless.
Review endpoint controls for archive extraction and executable launch monitoring.
Validation and detection
Confirm installed WinRAR versions on managed endpoints and compare against vendor guidance.
Test detection coverage using benign archive-handling scenarios, not weaponized samples.
Review email, proxy, and EDR logs for suspicious archive-to-executable activity.
Verify users cannot run executables from high-risk download locations where policy allows.
Check vulnerability management data for stale WinRAR installations.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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.
cwe · low confidence lookup
CWE-20: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
CWE-434: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
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.
1CVSS vectors
3Timeline events
1ADP providers
7Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-20 · source CWE mapping
Improper Input Validation
Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.