GHSA-f5c8-m5vw-rmgq — almirhodzic/nova-toggle-5
MEDIUMGHSA-f5c8-m5vw-rmgq is a medium-severity (CVSS 6.5) CWE-285 vulnerability in almirhodzic/nova-toggle-5. A fix is available for almirhodzic/nova-toggle-5 — see the affected versions and patch details below.
nova-toggle-5: Improper authorization on toggle endpoint allowed non-Nova users to modify boolean fields
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-f5c8-m5vw-rmgq.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-f5c8-m5vw-rmgq plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
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.0composer require almirhodzic/nova-toggle-5:^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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-f5c8-m5vw-rmgq can be triaged on real exposure rather than presence alone.
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 Security finds GHSA-f5c8-m5vw-rmgq across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.