Application crash via unchecked Add Pattern input
Published Apr 26, 2026 · Updated Apr 26, 2026
Buffer overflow in Editor Software StyleWriter 1.0 allows local users to crash the application through oversized Add Pattern input. The Add Pattern dialog copies a 6,000-byte string from either the Pattern to Find or Advice Message field without checking the destination buffer size. Access to the local graphical interface is required, and the demonstrated consequence is an application crash rather than code execution.
Summary
What happened
Buffer overflow in Editor Software StyleWriter 1.0 allows local users to crash the application through oversized Add Pattern input. The Add Pattern dialog copies a 6,000-byte string from either the Pattern to Find or Advice Message field without checking the destination buffer size. Access to the local graphical interface is required, and the demonstrated consequence is an application crash rather than code execution.
The record
- CVE
- CVE-2018-25288
- Published
- Apr 26, 2026
- Updated
- Apr 26, 2026
- Vendor
- Editor Software
- Product
- StyleWriter
- Classifications
- CWE-120, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 26, 2026CVE publishedPublication date reported by the CVE source.
- Apr 26, 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.0
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
- StyleWriter 4 1.0 - Denial of Service (PoC)proof of concept · 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