https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 08 Oct 2026 19:35:25 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-309877 EUVD-2026-309877 https://cve.radiocsirt.org/vuln/euvd-2026-309877 https://cve.radiocsirt.org/vuln/fkie_cve-2026-42202 <p>nova-toggle-5 enables fliping booleans in the index. Prior to version 1.3.0, the toggle endpoint (POST/nova-vendor/nova-toggle/toggle/{resource}/{resourceId}) was protected only by web + auth:&lt;guard&gt; middleware. Any user authenticated on the configured guard could call the endpoint and flip boolean attributes on any Nova resource — including users who do not have access to Nova itself (for example, frontend customers sharing the web guard with the Nova admin area). The endpoint also accepted an arbitrary attribute parameter, which meant a valid caller could toggle any boolean column on the underlying model — not just columns exposed as Toggle fields on the resource. This issue has been patched in version 1.3.0.</p> <p>nova-toggle-5 enables fliping booleans in the index. Prior to version 1.3.0, the toggle endpoint (POST/nova-vendor/nova-toggle/toggle/{resource}/{resourceId}) was protected only by web + auth:&lt;guard&gt; middleware. Any user authenticated on the configured guard could call the endpoint and flip boolean attributes on any Nova resource — including users who do not have access to Nova itself (for example, frontend customers sharing the web guard with the Nova admin area). The endpoint also accepted an arbitrary attribute parameter, which meant a valid caller could toggle any boolean column on the underlying model — not just columns exposed as Toggle fields on the resource. This issue has been patched in version 1.3.0.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-42202 https://cve.radiocsirt.org/vuln/ghsa-f5c8-m5vw-rmgq <p><strong>Affected:</strong> Packagist: almirhodzic/nova-toggle-5</p> <p>### Impact</p> <p>In versions `&lt; 1.3.0`, the toggle endpoint (`POST /nova-vendor/nova-toggle/toggle/{resource}/{resourceId}`) was protected only by `web` + `auth:&lt;guard&gt;` middleware. Any user authenticated on the configured guard could call the endpoint and flip boolean attributes on any Nova resource — including users who do not have access to Nova itself (for example, frontend customers sharing the `web` guard with the Nova admin area).</p> <p>The endpoint also accepted an arbitrary `attribute` parameter, which meant a valid caller could toggle any boolean column on the underlying model — not just columns exposed as `Toggle` fields on the resource.</p> <p>### Patches</p> <p>Fixed in `1.3.0`:</p> <p>- The route is now protected by Nova&#39;s `nova:api` middleware, which enforces the `viewNova` gate. - The controller now checks the resource&#39;s `authorizedToUpdate` policy. - The controller only accepts attributes that are declared as a `Toggle` field on the resource and are not readonly in the current request context.</p> <p>### Workarounds</p> <p>Users who cannot upgrade immediately can either remove the package or restrict access to the `/nova-vendor/nova-toggle/toggle/*` routes via an additional middleware in their application that enforces the `viewNova` gate.</p> <p>### Credits</p> <p>nova-toggle-5 thanks [Roberto Negro](https://github.com/RobertoNegro) for the responsible disclosure.</p> <p><strong>Affected:</strong> Packagist: almirhodzic/nova-toggle-5</p> <p>### Impact</p> <p>In versions `&lt; 1.3.0`, the toggle endpoint (`POST /nova-vendor/nova-toggle/toggle/{resource}/{resourceId}`) was protected only by `web` + `auth:&lt;guard&gt;` middleware. Any user authenticated on the configured guard could call the endpoint and flip boolean attributes on any Nova resource — including users who do not have access to Nova itself (for example, frontend customers sharing the `web` guard with the Nova admin area).</p> <p>The endpoint also accepted an arbitrary `attribute` parameter, which meant a valid caller could toggle any boolean column on the underlying model — not just columns exposed as `Toggle` fields on the resource.</p> <p>### Patches</p> <p>Fixed in `1.3.0`:</p> <p>- The route is now protected by Nova&#39;s `nova:api` middleware, which enforces the `viewNova` gate. - The controller now checks the resource&#39;s `authorizedToUpdate` policy. - The controller only accepts attributes that are declared as a `Toggle` field on the resource and are not readonly in the current request context.</p> <p>### Workarounds</p> <p>Users who cannot upgrade immediately can either remove the package or restrict access to the `/nova-vendor/nova-toggle/toggle/*` routes via an additional middleware in their application that enforces the `viewNova` gate.</p> <p>### Credits</p> <p>nova-toggle-5 thanks [Roberto Negro](https://github.com/RobertoNegro) for the responsible disclosure.</p> https://cve.radiocsirt.org/vuln/ghsa-f5c8-m5vw-rmgq