<?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>Mon, 28 Sep 2026 12:30:18 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-55065</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-55065</link>
      <description>&lt;p&gt;Vikunja is an open-source self-hosted task management platform. From 0.24.6 until 2.4.0, DELETE /api/v1/projects/:project/views/:view permits an authenticated user to supply a view identifier from another project while authorizing only against an attacker-controlled project identifier. ProjectView.CanDelete in pkg/models/project_view_permissions.go does not establish that the view belongs to the path project, and ProjectView.Delete in pkg/models/project_view.go continues after the scoped project_views delete affects no rows. Its subsequent deletes select task_buckets and task_positions only by project_view_id, allowing cross-tenant destruction of Kanban assignments and ordering while leaving the victim view and tasks intact. This issue is fixed in version 2.4.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Vikunja is an open-source self-hosted task management platform. From 0.24.6 until 2.4.0, DELETE /api/v1/projects/:project/views/:view permits an authenticated user to supply a view identifier from another project while authorizing only against an attacker-controlled project identifier. ProjectView.CanDelete in pkg/models/project_view_permissions.go does not establish that the view belongs to the path project, and ProjectView.Delete in pkg/models/project_view.go continues after the scoped project_views delete affects no rows. Its subsequent deletes select task_buckets and task_positions only by project_view_id, allowing cross-tenant destruction of Kanban assignments and ordering while leaving the victim view and tasks intact. This issue is fixed in version 2.4.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-55065</guid>
    </item>
    <item>
      <title>GHSA-gg93-x632-9ccv — Vikunja vulnerable to Improper Authorization and Authorization Bypass Through User-Controlled Key</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-gg93-x632-9ccv</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;A user with only a single self-owned project can permanently destroy the Kanban bucket assignments (`task_buckets`) and task ordering (`task_positions`) of **any other project view in the entire instance**. The `ProjectView.Delete` model method runs three SQL statements: the first is properly scoped to `(view_id, project_id)`, but the next two cascading deletes on `task_buckets` and `task_positions` filter only on the URL-supplied `project_view_id`. The permission check (`CanDelete`) gates on Admin of the URL `:project` but never confirms that the URL `:view` actually belongs to that project.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;`ProjectView.Delete` (file: `pkg/models/project_view.go`, line 250) cascades on the bare `pv.ID` for the second and third deletes, ignoring `pv.ProjectID`:&lt;/p&gt;
&lt;p&gt;```go
func (pv *ProjectView) Delete(s *xorm.Session, _ web.Auth) (err error) {
    _, err = s.
        Where(&amp;#34;id = ? AND project_id = ?&amp;#34;, pv.ID, pv.ProjectID).   // (a) scoped — OK
        Delete(&amp;amp;ProjectView{})
    if err != nil {
        return
    }&lt;/p&gt;
&lt;p&gt;_, err = s.Where(&amp;#34;project_view_id = ?&amp;#34;, pv.ID).Delete(&amp;amp;TaskBucket{})    // (b) UNSCOPED
    if err != nil {
        return
    }&lt;/p&gt;
&lt;p&gt;_, err = s.Where(&amp;#34;project_view_id = ?&amp;#34;, pv.ID).Delete(&amp;amp;TaskPosition{})  // (c) UNSCOPED
    return
}
```&lt;/p&gt;
&lt;p&gt;`pv.ID` and `pv.ProjectID` come straight from the URL path via `c.Bind` — see the param tags on the struct (`pkg/models/project_view.go`, lines 133–137):&lt;/p&gt;
&lt;p&gt;```go
type ProjectView struct {
    ID        int64 `xorm:&amp;#34;aut…&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;A user with only a single self-owned project can permanently destroy the Kanban bucket assignments (`task_buckets`) and task ordering (`task_positions`) of **any other project view in the entire instance**. The `ProjectView.Delete` model method runs three SQL statements: the first is properly scoped to `(view_id, project_id)`, but the next two cascading deletes on `task_buckets` and `task_positions` filter only on the URL-supplied `project_view_id`. The permission check (`CanDelete`) gates on Admin of the URL `:project` but never confirms that the URL `:view` actually belongs to that project.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;`ProjectView.Delete` (file: `pkg/models/project_view.go`, line 250) cascades on the bare `pv.ID` for the second and third deletes, ignoring `pv.ProjectID`:&lt;/p&gt;
&lt;p&gt;```go
func (pv *ProjectView) Delete(s *xorm.Session, _ web.Auth) (err error) {
    _, err = s.
        Where(&amp;#34;id = ? AND project_id = ?&amp;#34;, pv.ID, pv.ProjectID).   // (a) scoped — OK
        Delete(&amp;amp;ProjectView{})
    if err != nil {
        return
    }&lt;/p&gt;
&lt;p&gt;_, err = s.Where(&amp;#34;project_view_id = ?&amp;#34;, pv.ID).Delete(&amp;amp;TaskBucket{})    // (b) UNSCOPED
    if err != nil {
        return
    }&lt;/p&gt;
&lt;p&gt;_, err = s.Where(&amp;#34;project_view_id = ?&amp;#34;, pv.ID).Delete(&amp;amp;TaskPosition{})  // (c) UNSCOPED
    return
}
```&lt;/p&gt;
&lt;p&gt;`pv.ID` and `pv.ProjectID` come straight from the URL path via `c.Bind` — see the param tags on the struct (`pkg/models/project_view.go`, lines 133–137):&lt;/p&gt;
&lt;p&gt;```go
type ProjectView struct {
    ID        int64 `xorm:&amp;#34;aut…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-gg93-x632-9ccv</guid>
    </item>
  </channel>
</rss>
