SQL Injection in winter/wn-backend-module (CVE-2026-32593)
Summary
SQL injection in winter/wn-backend-module (CVE-2026-32593). Confidential information can be exposed externally. Exploitable via numberrange. Mitigation: upgrade to 1.2.13 or later.
Original description
The description as published by the source.
Impact
The Backend Filter widget (Backend\Widgets\Filter) is vulnerable to SQL injection through the numberrange scope type when the scope is configured with a conditions key. An authenticated backend user with access to a list view containing a vulnerable filter scope can inject arbitrary SQL via the filter's AJAX handler, potentially gaining read access to the full database contents.
To exploit this, an attacker must have a valid backend account with access to a list view where a third-party plugin has registered a numberrange filter scope using the conditions configuration key. No built-in Winter CMS backend views use this scope type and configuration combination, so a vanilla installation without plugins is not exploitable.
Patches
This issue has been fixed in Winter CMS v1.2.13.
Workarounds
If users cannot upgrade, they may apply commit https://github.com/wintercms/winter/commit/50713de95adf5298536d93f4d999652525d36d43 to your Winter CMS
installation manually to resolve this issue.
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-32593 has been found in winter/wn-backend-module.
Attackers can target a specific entry point like numberrange over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.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-32593" on the vendor's site.
CVE-2026-32593 (winter/wn-backend-module) — CWE-89 / CVSS v3 5.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: numberrange / conditions
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.
SQL injection (CWE-89) exists in winter/wn-backend-module. Attackers reach the vulnerable code path via numberrange.
Check the vendor advisory for the affected versions of winter/wn-backend-module. Attack surface: numberrange / conditions.
Severity: Medium (CVSS 5.9/10). Confidential information can be exposed externally.
Update to 1.2.13.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade winter/wn-backend-module to 1.2.13ステージング環境で 1.2.13 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com
- web github.com