| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-f5c8-m5vw-rmgq | nova-toggle-5: Improper authorization on toggle endpoint allowed non-Nova users to modify boolean fields |
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Mon, 11 May 2026 15:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Sun, 10 May 2026 21:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Almirhodzic
Almirhodzic nova-toggle-5 |
|
| Vendors & Products |
Almirhodzic
Almirhodzic nova-toggle-5 |
Fri, 08 May 2026 21:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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:<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. This issue has been patched in version 1.3.0. | |
| Title | nova-toggle-5: Improper authorization on toggle endpoint allowed non-Nova users to modify boolean fields | |
| Weaknesses | CWE-285 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-05-11T14:24:49.712Z
Reserved: 2026-04-25T05:04:37.027Z
Link: CVE-2026-42202
Updated: 2026-05-11T14:24:43.427Z
Status : Deferred
Published: 2026-05-08T22:16:31.683
Modified: 2026-05-13T16:34:42.677
Link: CVE-2026-42202
No data.
OpenCVE Enrichment
Updated: 2026-05-10T21:24:51Z
Github GHSA