Writediary maintains a focused personal diary application with encryption and access controls, where the durable signal centers on data-protection implementation issues such as missing encryption of sensitive data and use of hard-coded credentials. Treat this as a compact vendor profile rather than a broad trend line; live severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Writediary over time
Signals from CVEs in this vendor scope (2 CVEs).
2 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2017-15582HIGH In net.MCrypt in the "Diary with lock" (aka WriteDiary) application 4.72 for Android, hardcoded SecretKey and iv variables are used for the AES parameters, which makes it easier fo | Oct 27, 2017 | 7.5 | 23 | NO | NO |
CVE-2017-15581HIGH In the "Diary with lock" (aka WriteDiary) application 4.72 for Android, neither HTTPS nor other encryption is used for transmitting data, despite the documentation that the product | Oct 27, 2017 | 7.5 | 23 | NO | NO |
Signals from CVEs in this vendor scope (2 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Writediary.
Media articles that mention a CVE ID that affects a product developed by Writediary — matched by CVE ID, not by vendor name.