https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 07 Oct 2026 18:01:17 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-273575 EUVD-2026-273575 https://cve.radiocsirt.org/vuln/euvd-2026-273575 https://cve.radiocsirt.org/vuln/fkie_cve-2026-27575 <p>Vikunja is an open-source self-hosted task management platform. Prior to version 2.0.0, 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. Version 2.0.0 contains a fix.</p> <p>Vikunja is an open-source self-hosted task management platform. Prior to version 2.0.0, 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. Version 2.0.0 contains a fix.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-27575 https://cve.radiocsirt.org/vuln/ghsa-3ccg-x393-96v8 <p><strong>Affected:</strong> Go: code.vikunja.io/api</p> <p>**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.</p> <p>An attacker who compromises an account (via brute-force or credential stuffing) can maintain persistent access even after the victim resets their password.</p> <p>**Details**</p> <p>1. Weak passwords are accepted during registration and password change. 2. No minimum length or strength validation is enforced. 3. After changing the password, previously issued session tokens remain valid. 4. No forced logout occurs across active sessions.</p> <p>_Attack scenario:_</p> <p>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.</p> <p>**Steps to Reproduce**</p> <p>**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.</p> <p>**Impact**</p> <p>- Persistent account takeover - Unauthorized access to sensitive data - Increased brute-force success probability - Elevated risk for administrative accounts</p> <p>The combination of weak password controls and improper session invalidation significantly increases both exploitability and impact.</p> <p>**Recommendation** _**Password Policy Improvements:**_</p> <p>- Enforce strong pa…</p> <p><strong>Affected:</strong> Go: code.vikunja.io/api</p> <p>**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.</p> <p>An attacker who compromises an account (via brute-force or credential stuffing) can maintain persistent access even after the victim resets their password.</p> <p>**Details**</p> <p>1. Weak passwords are accepted during registration and password change. 2. No minimum length or strength validation is enforced. 3. After changing the password, previously issued session tokens remain valid. 4. No forced logout occurs across active sessions.</p> <p>_Attack scenario:_</p> <p>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.</p> <p>**Steps to Reproduce**</p> <p>**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.</p> <p>**Impact**</p> <p>- Persistent account takeover - Unauthorized access to sensitive data - Increased brute-force success probability - Elevated risk for administrative accounts</p> <p>The combination of weak password controls and improper session invalidation significantly increases both exploitability and impact.</p> <p>**Recommendation** _**Password Policy Improvements:**_</p> <p>- Enforce strong pa…</p> https://cve.radiocsirt.org/vuln/ghsa-3ccg-x393-96v8