License-key disclosure via uncleared activation memory
Published Oct 27, 2025 · Updated Oct 27, 2025
Cleartext license-key storage in Easywork Enterprise 2.1.3.354 allows local users to read valid keys from process memory. After a failed activation attempt, the application retains a valid device-bound license key instead of clearing it from memory. Exploitation requires local debugger or process-dump access, and the recovered key activates the software only on the same machine.
Summary
What happened
Cleartext license-key storage in Easywork Enterprise 2.1.3.354 allows local users to read valid keys from process memory. After a failed activation attempt, the application retains a valid device-bound license key instead of clearing it from memory. Exploitation requires local debugger or process-dump access, and the recovered key activates the software only on the same machine.
The record
- CVE
- CVE-2025-60791
- Published
- Oct 27, 2025
- Updated
- Oct 27, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-316
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 27, 2025CVE publishedPublication date reported by the CVE source.
- Oct 27, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Easywork Enterprise license-key exposure proof of conceptproof of concept · unverified
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