Local code execution via wow64log DLL planting
Published Dec 18, 2025 · Updated Dec 18, 2025
DLL search-order hijacking in Hubstaff 1.6.13 and 1.6.14 allows local users to execute code by planting wow64log.dll. The Windows setup executable requests a missing wow64log.dll from System32 and loads an attacker-supplied library placed there. Exploitation requires local access and permission to write the library into System32; launching the executable runs its payload in the application process.
Summary
What happened
DLL search-order hijacking in Hubstaff 1.6.13 and 1.6.14 allows local users to execute code by planting wow64log.dll. The Windows setup executable requests a missing wow64log.dll from System32 and loads an attacker-supplied library placed there. Exploitation requires local access and permission to write the library into System32; launching the executable runs its payload in the application process.
The record
- CVE
- CVE-2023-53937
- Published
- Dec 18, 2025
- Updated
- Dec 18, 2025
- Vendor
- Hubstaff
- Product
- Hubstaff
- Classifications
- CWE-427, T1574.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 18, 2025CVE publishedPublication date reported by the CVE source.
- Dec 18, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.6.13, 1.6.14
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Hubstaff wow64log DLL Search Order Hijackingfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo