Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-42202 medium CVSS 6.5

Vulnerability in almirhodzic/nova-toggle-5 (CVE-2026-42202)

Summary

Vulnerability in almirhodzic/nova-toggle-5 (CVE-2026-42202). Data can be tampered with by attackers. Exploitable via POST /nova-vendor/nova-toggle/toggle/{resource}/{resourceId}. Mitigation: upgrade to 1.3.0 or later.

Original description

The description as published by the source.

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: 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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-42202 has been found in almirhodzic/nova-toggle-5.
Attackers can target a specific entry point like POST /nova-vendor/nova-toggle/toggle/{resource}/{resourceId} over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 6.5/10.
What to do: upgrade almirhodzic/nova-toggle-5 to 1.3.0 or later.
If unsure, ask your IT team or search "almirhodzic/nova-toggle-5 CVE-2026-42202" on the vendor's site.

CVE-2026-42202 (almirhodzic/nova-toggle-5) — CWE-285 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /nova-vendor/nova-toggle/toggle/{resource}/{resourceId} / web / attribute / Toggle
Patched: 1.3.0 — apply immediately
Workaround: 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.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-285) exists in almirhodzic/nova-toggle-5. Attackers reach the vulnerable code path via POST /nova-vendor/nova-toggle/toggle/{resource}/{resourceId}.

📍 Affected scope

Check the vendor advisory for the affected versions of almirhodzic/nova-toggle-5. Attack surface: POST /nova-vendor/nova-toggle/toggle/{resource}/{resourceId} / web / attribute / Toggle.

🔥 Severity

Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers.

🔧 How to fix

Update to 1.3.0.

🛡️ Workaround

Workaround: 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.

🔍 Detection

Search webserver/proxy logs for unusual POST /nova-vendor/nova-toggle/toggle/{resource}/{resourceId} requests with malformed payloads or SQL meta-characters. Run grep -r 'almirhodzic/nova-toggle-5' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'almirhodzic/nova-toggle-5' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で almirhodzic/nova-toggle-5 を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'POST /nova-vendor/nova-toggle/toggle/{resource}/{resourceId}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで POST /nova-vendor/nova-toggle/toggle/{resource}/{resourceId} への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply temporary workaround mitigate 
    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.

    パッチが適用されるまでの応急処置として、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. を実施。回避策の副作用 (機能低下) を確認した上で。

  4. 4
    Apply patch patch 
    Upgrade almirhodzic/nova-toggle-5 to 1.3.0

    ステージング環境で 1.3.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  5. 5
    Post-deployment verification verify 
    Replay attack against POST /nova-vendor/nova-toggle/toggle/{resource}/{resourceId} on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

composer almirhodzic/nova-toggle-5
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.3.0"}]}]
Packagist almirhodzic/nova-toggle-5
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.3.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details