code.vikunja.io/api
Affected
- introduced
0, last affected0.24.6(semver)
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: CVE-2026-27575, GO-2026-4551
Vijkunja has Weak Password Policy Combined with Persistent Sessions After Password Change
Summary
The application allows users to set weak passwords (e.g., 1234, password) without enforcing minimum strength requirements. Additionally, active sessions remain valid after a user changes their password.
An attacker who compromises an account (via brute-force or credential stuffing) can maintain persistent access even after the victim resets their password.
Details
_Attack scenario:_
Attacker guesses or obtains weak credentials.
Logs in and obtains active session token.
Victim changes password.
Attacker continues accessing the account using the old session.
Steps to Reproduce
1. Register using a weak password (e.g., 12345678 ).
2. Log in and Password Change functionality.
3. Change account password with single character (e.g., 1 or a )
4. Reuse the old session.
5. Observe that access is still granted.
Impact
The combination of weak password controls and improper session invalidation significantly increases both exploitability and impact.
Recommendation
_Password Policy Improvements:_
_Session Management Fix:_
Implementing both controls will significantly reduce the risk of persistent account compromise.
<img width="1918" height="907" alt="Weak Password Policy Combined with Persistent Sessions After Password Change POC" src="https://github.com/user-attachments/assets/f188b69b-0472-4d2c-aeda-c145384c99ef" />
A fixed version is available at https://github.com/go-vikunja/vikunja/releases/tag/v2.0.0.
Critical Basis: The source's own band: CRITICAL
0, last affected 0.24.6 (semver)None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0