<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 10 Oct 2026 13:10:19 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-62376</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-62376</link>
      <description>&lt;p&gt;Vikunja is an open-source self-hosted task management platform. Versions prior to 2.4.0 store password-reset, email-confirmation, and account-deletion tokens in the `user_tokens` table in plaintext. If an attacker gains read access to the database through a backup leak, misconfigured storage, or SQL-level exposure, they can immediately use pending tokens to take over user accounts without knowing passwords. Version 2.4.0 fixes the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Vikunja is an open-source self-hosted task management platform. Versions prior to 2.4.0 store password-reset, email-confirmation, and account-deletion tokens in the `user_tokens` table in plaintext. If an attacker gains read access to the database through a backup leak, misconfigured storage, or SQL-level exposure, they can immediately use pending tokens to take over user accounts without knowing passwords. Version 2.4.0 fixes the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-62376</guid>
    </item>
    <item>
      <title>GHSA-r6w9-259g-gwrv — Vikunja: Plaintext storage of password-reset/email-confirm tokens in database enables account takeover on DB read access</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-r6w9-259g-gwrv</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: code.vikunja.io/api&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Vikunja stores password-reset, email-confirmation, and account-deletion tokens in the `user_tokens` table in **plaintext**. If an attacker gains read access to the database through a backup leak, misconfigured storage, or SQL-level exposure, they can immediately use pending tokens to take over user accounts without knowing passwords.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;`pkg/user/token.go` — `genToken()` stores the raw random string directly:
```go
func genToken(u *User, kind TokenKind) (*Token, error) {
    tokenStr, err := utils.CryptoRandomString(tokenSize)
    ...
    return &amp;amp;Token{
        UserID: u.ID,
        Kind:   kind,
        Token:  tokenStr,  // stored as-is, no hashing
    }, nil
}
```&lt;/p&gt;
&lt;p&gt;Lookup also uses plaintext equality:
```go
func getToken(s *xorm.Session, token string, kind TokenKind) (t *Token, err error) {
    has, err := s.Where(&amp;#34;kind = ? AND token = ?&amp;#34;, kind, token).Get(t)
}
```&lt;/p&gt;
&lt;p&gt;Affected token types:
- `TokenPasswordReset` (`pkg/user/user_password_reset.go:120`)
- `TokenEmailConfirm` (`pkg/user/user_create.go:101`, `pkg/user/update_email.go:88`)
- `TokenAccountDeletion` (`pkg/user/delete.go:102`)&lt;/p&gt;
&lt;p&gt;Note: CalDAV tokens correctly use `generateHashedToken` with bcrypt — the same protection is absent for the above types.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;```sql
-- Attacker with DB read dumps all pending password-reset tokens:
SELECT u.email, t.token FROM user_tokens t
JOIN users u ON u.id = t.user_id WHERE t.kind = 1;&lt;/p&gt;
&lt;p&gt;-- Then takes over any account:
curl -X POST https://vikunja.example.co…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: code.vikunja.io/api&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Vikunja stores password-reset, email-confirmation, and account-deletion tokens in the `user_tokens` table in **plaintext**. If an attacker gains read access to the database through a backup leak, misconfigured storage, or SQL-level exposure, they can immediately use pending tokens to take over user accounts without knowing passwords.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;`pkg/user/token.go` — `genToken()` stores the raw random string directly:
```go
func genToken(u *User, kind TokenKind) (*Token, error) {
    tokenStr, err := utils.CryptoRandomString(tokenSize)
    ...
    return &amp;amp;Token{
        UserID: u.ID,
        Kind:   kind,
        Token:  tokenStr,  // stored as-is, no hashing
    }, nil
}
```&lt;/p&gt;
&lt;p&gt;Lookup also uses plaintext equality:
```go
func getToken(s *xorm.Session, token string, kind TokenKind) (t *Token, err error) {
    has, err := s.Where(&amp;#34;kind = ? AND token = ?&amp;#34;, kind, token).Get(t)
}
```&lt;/p&gt;
&lt;p&gt;Affected token types:
- `TokenPasswordReset` (`pkg/user/user_password_reset.go:120`)
- `TokenEmailConfirm` (`pkg/user/user_create.go:101`, `pkg/user/update_email.go:88`)
- `TokenAccountDeletion` (`pkg/user/delete.go:102`)&lt;/p&gt;
&lt;p&gt;Note: CalDAV tokens correctly use `generateHashedToken` with bcrypt — the same protection is absent for the above types.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;```sql
-- Attacker with DB read dumps all pending password-reset tokens:
SELECT u.email, t.token FROM user_tokens t
JOIN users u ON u.id = t.user_id WHERE t.kind = 1;&lt;/p&gt;
&lt;p&gt;-- Then takes over any account:
curl -X POST https://vikunja.example.co…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-r6w9-259g-gwrv</guid>
    </item>
  </channel>
</rss>
