almirhodzic/nova-toggle-5
Affected
- introduced
0, fixed1.3.0(ecosystem)
Fixed versions
1.3.0
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2026-42202
nova-toggle-5: Improper authorization on toggle endpoint allowed non-Nova users to modify boolean fields
Impact
In versions < 1.3.0, the toggle endpoint (POST /nova-vendor/nova-toggle/toggle/{resource}/{resourceId}) was protected only by web + auth:<guard> 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.
Patches
Fixed in 1.3.0:
nova:api middleware, which enforces the viewNova gate.authorizedToUpdate policy.Toggle field on the resource and are not readonly in the current request context.Workarounds
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.
Credits
nova-toggle-5 thanks Roberto Negro for the responsible disclosure.
Medium Basis: The source's own band: MODERATE
0, fixed 1.3.0 (ecosystem)1.3.0
The export has no generic command for this ecosystem.
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