← Back
GHSA-7mpf-4465-7fc2
Cross-Site Scripting (XSS) in winter/wn-backend-module (GHSA-7mpf-4465-7fc2)
Summary
cross-site scripting in winter/wn-backend-module (GHSA-7mpf-4465-7fc2). Risk of unauthorized operations or information disclosure. Exploitable via ``src``. Mitigation: upgrade to `1.2.14` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-7mpf-4465-7fc2** has been found in winter/wn-backend-module.
Attackers can target a specific entry point like ``src`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade winter/wn-backend-module to **1.2.14** or later.
If unsure, ask your IT team or search "winter/wn-backend-module GHSA-7mpf-4465-7fc2" on the vendor's site.
GHSA-7mpf-4465-7fc2 (winter/wn-backend-module) — CWE-79 /
Attack surface: `src` / `image`
Patched: `1.2.14` — apply immediately
Workaround: Apply the commit above to `modules/backend/widgets/Lists.php` manually if you are unable to upgrade to v1.2.14.
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
**Cross-site scripting (XSS)** (CWE-79) exists in winter/wn-backend-module. Attackers reach the vulnerable code path via ``src`` without authentication.
📍 Affected scope
winter/wn-backend-module — . Attack surface: `src` / `image`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.2.14**.
🛡️ Workaround
Workaround: Apply the commit above to `modules/backend/widgets/Lists.php` manually if you are unable to upgrade to v1.2.14.
🔍 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
-
1Identify 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 し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Apply the commit above to `modules/backend/widgets/Lists.php` manually if you are unable to upgrade to v1.2.14.パッチが適用されるまでの応急処置として、Apply the commit above to `modules/backend/widgets/Lists.php` manually if you are unable to upgrade to v1.2.14. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade winter/wn-backend-module to 1.2.14ステージング環境で 1.2.14 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-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.14"}]}]