Vikunja
Vikunja before 2.7.1 Sensitive Token Exposure via URL Query in Access Logs
Vikunja before 2.7.1 embeds live password-reset, email-confirmation and account-deletion tokens in the URL query string of emailed links, so the full request URI, including the token, is written to Vikunja's HTTP access log and any reverse-proxy logs when a user clicks the link. Attackers with read access to those logs can replay an unredeemed password-reset token to take over the account or an account-deletion token to confirm the deletion.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.4high · scored by CNA · CWE-532
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
go-vikunja vikunja
- < 2.7.1
Fixed in 2.7.1
Mitigation
Upgrade vikunja to 2.7.1 or later.
References
- Vendor advisory github.com/go-vikunja/vikunja/security/advisor…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.