Local code execution via oversized command-line argument
Published Mar 28, 2026 · Updated Mar 28, 2026
Stack-based buffer overflow in Identical Software xwpe 1.5.30a-2.1 and earlier allows local users to execute code via a long argument. The command-line argument path accepts user-supplied strings beyond the stack buffer boundary, allowing saved EIP to be overwritten after 262 bytes. Local access is required, and successful exploitation runs code in the application user context; failed attempts crash the editor.
Summary
What happened
Stack-based buffer overflow in Identical Software xwpe 1.5.30a-2.1 and earlier allows local users to execute code via a long argument. The command-line argument path accepts user-supplied strings beyond the stack buffer boundary, allowing saved EIP to be overwritten after 262 bytes. Local access is required, and successful exploitation runs code in the application user context; failed attempts crash the editor.
The record
- CVE
- CVE-2016-20037
- Published
- Mar 28, 2026
- Updated
- Mar 28, 2026
- Vendor
- Identical Software
- Product
- xwpe
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 28, 2026CVE publishedPublication date reported by the CVE source.
- Mar 28, 2026Record 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.5.30a-2.1
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.
Public exploit references
- xWPE 1.5.30a-2.1 Local Buffer Overflowfunctional · 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