Memory corruption via unchecked PRJ file bounds
Published Jun 17, 2025 · Updated Jun 4, 2026
Out-of-bounds write in LS Electric GMWIN 4.18 allows local users to corrupt memory through a crafted PRJ project file. The PRJ parser fails to validate user-supplied values before accessing allocated data structures, permitting reads and writes beyond their bounds. Exploitation requires a user to open the file and can disclose, alter, or corrupt process memory or crash the application.
Summary
What happened
Out-of-bounds write in LS Electric GMWIN 4.18 allows local users to corrupt memory through a crafted PRJ project file. The PRJ parser fails to validate user-supplied values before accessing allocated data structures, permitting reads and writes beyond their bounds. Exploitation requires a user to open the file and can disclose, alter, or corrupt process memory or crash the application.
The record
- CVE
- CVE-2025-49848
- Published
- Jun 17, 2025
- Updated
- Jun 4, 2026
- Vendor
- LS ELECTRIC
- Product
- GMWIN
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 17, 2025CVE publishedPublication date reported by the CVE source.
- Jun 4, 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=Version 4.18
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
No public exploit references are available in this record.
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