Account takeover via weak default JWT secret
Published May 17, 2025 · Updated May 19, 2025
Authentication bypass in Donetick before 0.1.44 allows remote attackers to take over any account by forging a signed JWT. The JWT authentication configuration supplies a weak default HS256 signing secret, causing middleware to accept attacker-signed tokens carrying another username. Exploitation requires network access but no existing account or user interaction, and permits reading and modifying data as the impersonated user.
Summary
What happened
Authentication bypass in Donetick before 0.1.44 allows remote attackers to take over any account by forging a signed JWT. The JWT authentication configuration supplies a weak default HS256 signing secret, causing middleware to accept attacker-signed tokens carrying another username. Exploitation requires network access but no existing account or user interaction, and permits reading and modifying data as the impersonated user.
The record
- CVE
- CVE-2025-47945
- Published
- May 17, 2025
- Updated
- May 19, 2025
- Vendor
- Donetick
- Product
- Donetick
- Classifications
- CWE-1188, CWE-453, T1606
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 17, 2025CVE publishedPublication date reported by the CVE source.
- May 19, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.1.44
What conditions does exploitation require?
What is affected?
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
- GitHub advisory JWT-forgery proof of conceptproof 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