dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2026-42202

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The nova-toggle-5 package had a broken access control vulnerability where the toggle endpoint (POST /nova-vendor/nova-toggle/toggle/{resource}/{resourceId}) was protected only by web + auth middleware, allowing any authenticated user on the configured guard to flip arbitrary boolean attributes on any Nova resource — including frontend customers who should not have access to Nova admin functionality.

MitigationUpgrade to version 1.3.0 immediately. Additionally, audit user access controls and ensure Nova-specific authorization policies are in place to prevent authenticated web users from accessing administrative functionality.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check nova-toggle package version
    Run composer show nova-toggle/nova-toggle-5 or check your composer.lock for the installed version of nova-toggle/nova-toggle-5
    Affected if Installed version is below 1.3.0
  2. Verify toggle endpoint is accessible
    Inspect the routes/nova-toggle.php or check if the route POST /nova-vendor/nova-toggle/toggle/{resource}/{resourceId} is registered without Nova-specific policy middleware
    Affected if The route exists and lacks Nova authorization policy enforcement (only has web or auth middleware)
  3. Review Nova authorization policies
    Check your Nova resources for any Gate or Policy definitions that should restrict the toggle endpoint to admin users only
    Affected if No Nova-specific authorization policy restricts toggle access to authorized administrators
  4. Audit authenticated user roles
    Review which user roles have web authentication but should not have access to Nova admin functionality
    Affected if Regular authenticated users (non-admins) can access Nova routes or the toggle endpoint

You are affected if nova-toggle-5 version is below 1.3.0 AND the toggle endpoint lacks Nova-specific authorization policies, allowing any authenticated user to modify arbitrary resource attributes.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 1.3.0 immediately. Additionally, audit user access controls and ensure Nova-specific authorization policies are in place to prevent authenticated web users from accessing administrative functionality.

Recommended fix High confidence

1.3.0

  1. Run `composer require nova-toggle/nova-toggle:^1.3.0` or `composer require nova-toggle/nova-toggle:^1.3` to update to the patched version
  2. Run `composer update nova-toggle/nova-toggle` to apply the changes
  3. Clear Laravel's cached files if needed: `php artisan config:clear` and `php artisan cache:clear`
  4. Verify the upgrade by checking the installed version with `composer show nova-toggle/nova-toggle`

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-42202 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-42202 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data