Sign in Sign up
JA · EN · FR
SecPulse
← Back
CVE-2026-63179 medium CVSS 4.9

Path Traversal in winter/wn-backend-module (CVE-2026-63179)

Summary

path traversal in winter/wn-backend-module (CVE-2026-63179). Confidential information can be exposed externally. Exploitable via ``BrandSetting.custom_css``. Mitigation: upgrade to `1.2.13` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-63179** has been found in winter/wn-backend-module. Attackers can target a specific entry point like ``BrandSetting.custom_css`` over the network to misuse the product. Confidential information can be exposed externally. CVSS score: 4.9/10. What to do: upgrade winter/wn-backend-module to **1.2.13** or later. If unsure, ask your IT team or search "winter/wn-backend-module CVE-2026-63179" on the vendor's site.
CVE-2026-63179 (winter/wn-backend-module) — CWE-22 / CVSS v3 4.9 Attack vector: remote (network-reachable) / no user interaction Attack surface: `BrandSetting.custom_css` / `backend.manage_branding` / `EditorSetting.html_custom_styles` / `backend.manage_editor` Patched: `1.2.13` — apply immediately Workaround: If you cannot upgrade, apply https://github.com/wintercms/storm/commit/af770331c683e628533a6ec2991285d6e10a4d6c and https://github.com/wintercms/winter/commit/130f0ea43e9228bf0d129b481da1cdfbcc4b4456 manually. 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
**Path traversal** (CWE-22) exists in winter/wn-backend-module. Attackers reach the vulnerable code path via ``BrandSetting.custom_css`` without authentication.
📍 Affected scope
winter/wn-backend-module — . Attack surface: `BrandSetting.custom_css` / `backend.manage_branding` / `EditorSetting.html_custom_styles` / `backend.manage_editor`.
🔥 Severity
Severity: Medium (CVSS 4.9/10). Confidential information can be exposed externally
🔧 How to fix
Update to **1.2.13**.
🛡️ Workaround
Workaround: If you cannot upgrade, apply https://github.com/wintercms/storm/commit/af770331c683e628533a6ec2991285d6e10a4d6c and https://github.com/wintercms/winter/commit/130f0ea43e9228bf0d129b481da1cdfbcc4b4456 manually.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'winter/wn-backend-module' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

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

  1. 1
    Identify exposure identify 
    grep -r 'winter/wn-backend-module' . | grep -v node_modules

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

  2. 5
    Apply temporary workaround mitigate 
    If you cannot upgrade, apply https://github.com/wintercms/storm/commit/af770331c683e628533a6ec2991285d6e10a4d6c and https://github.com/wintercms/winter/commit/130f0ea43e9228bf0d129b481da1cdfbcc4b4456 manually.

    パッチが適用されるまでの応急処置として、If you cannot upgrade, apply https://github.com/wintercms/storm/commit/af770331c683e628533a6ec2991285d6e10a4d6c and https://github.com/wintercms/winter/commit/130f0ea43e9228bf0d129b481da1cdfbcc4b4456 manually. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 6
    Apply patch patch 
    Upgrade winter/wn-backend-module to 1.2.13

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

  4. 7
    Post-deployment verification verify 
    Confirm patched version is live in production

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

Affected packages

composer winter/wn-backend-module
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.2.13"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →