GHSA-f5c8-m5vw-rmgq
MEDIUMGHSA-f5c8-m5vw-rmgq is a medium-severity (CVSS 6.5) vulnerability in almirhodzic/nova-toggle-5. O3 Security confirms whether GHSA-f5c8-m5vw-rmgq is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
nova-toggle-5: Improper authorization on toggle endpoint allowed non-Nova users to modify boolean fields
Blast Radius
almirhodzic/nova-toggle-5Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
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:
- The route is now protected by Nova's
nova:apimiddleware, which enforces theviewNovagate. - The controller now checks the resource's
authorizedToUpdatepolicy. - The controller only accepts attributes that are declared as a
Togglefield 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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | almirhodzic/nova-toggle-5 | all versions | 1.3.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for almirhodzic/nova-toggle-5. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update almirhodzic/nova-toggle-5 to 1.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f5c8-m5vw-rmgq is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-f5c8-m5vw-rmgq is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-f5c8-m5vw-rmgq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-f5c8-m5vw-rmgq in your dependencies?
O3 detects GHSA-f5c8-m5vw-rmgq across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.