Categories
CVE-2026-32639 medium CVSS 6.8

Vulnerability in winter/wn-cms-module (CVE-2026-32639)

Summary

Vulnerability in winter/wn-cms-module (CVE-2026-32639). Confidential information can be exposed externally. Exploitable via cms.manage_pages. Mitigation: upgrade to 1.2.13 or later.

Original description

The description as published by the source.

Impact

Affected versions of Winter CMS did not enforce per-template-type permission checks in the CMS section's AJAX handlers. The CMS controller (Cms\Controllers\Index) used OR-logic across its five permissions (cms.manage_pages, cms.manage_partials, cms.manage_layouts, cms.manage_content, cms.manage_assets) to control access to the section as a whole, but individual handlers such as onSave(), onDelete(), and onDeleteTemplates() did not verify that the authenticated user holds the specific permission corresponding to the requested template type.

This allowed a backend user with any single Theme Editor permission (e.g. cms.manage_pages) to craft AJAX requests targeting template types outside their authorized scope — for example, deleting layouts, modifying partials, or reading content files.

In addition, the AssetList widget was registered for all users who passed the controller gate regardless of whether they held the cms.manage_assets permission, and its onUpload() handler was missing the validateRequestTheme() call that is present on all other mutating handlers in the same widget. This allowed unauthorized file uploads into the active theme's asset directory.

To actively exploit this security issue, an attacker would need access to the Backend with a user account with any of the following permissions:

  • cms.manage_pages
  • cms.manage_partials
  • cms.manage_layouts
  • cms.manage_content
  • cms.manage_assets

The Winter CMS maintain…

Source: GitHub Security Advisories (Global) 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-32639 has been found in winter/wn-cms-module.
Attackers can target a specific entry point like cms.manage_pages over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.8/10.
What to do: upgrade winter/wn-cms-module to 1.2.13 or later.
If unsure, ask your IT team or search "winter/wn-cms-module CVE-2026-32639" on the vendor's site.

CVE-2026-32639 (winter/wn-cms-module) — CWE-289 / CVSS v3 6.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: cms.manage_pages / cms.manage_partials / cms.manage_layouts / cms.manage_content
Patched: 1.2.13 — apply immediately
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-289) exists in winter/wn-cms-module. Attackers reach the vulnerable code path via cms.manage_pages.

📍 Affected scope

Check the vendor advisory for the affected versions of winter/wn-cms-module. Attack surface: cms.manage_pages / cms.manage_partials / cms.manage_layouts / cms.manage_content.

🔥 Severity

Severity: Medium (CVSS 6.8/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 1.2.13.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'winter/wn-cms-module' . 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 'winter/wn-cms-module' . | grep -v node_modules

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

  2. 2
    Apply patch patch
    Upgrade winter/wn-cms-module to 1.2.13

    ステージング環境で 1.2.13 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

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

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

Affected packages

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

References

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