Winter: SQL Injection in Backend Filter Widget numberrange Scope via numbersFromAjax

TRUNG BÌNH 5.9CVE-2026-32593 · GHSA-m7jc-g4rc-jmvh · Công bố 26/08/2026 · cập nhật 09/09/2026

Tóm tắt nhanh

CVE-2026-32593 là lỗ hổng mức TRUNG BÌNH (CVSS 5.9) ảnh hưởng winter/wn-backend-module.
Xác suất bị khai thác trong 30 ngày tới (EPSS): 0.27%, cao hơn 19.8% các lỗ hổng khác.
Cách xử lý: cập nhật lên 1.2.13 hoặc mới hơn.

Gói / sản phẩm	Phiên bản bị ảnh hưởng	Phiên bản đã vá
winter/wn-backend-module Packagist	`< 1.2.13`	`1.2.13`

Mô tả

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.

Mô tả của NVD

Winter CMS is a content management system built on the Laravel PHP framework. In versions up to and including 1.2.12, the backend Filter widget is vulnerable to SQL injection through the numberrange scope type when that scope is configured with a conditions key, allowing an authenticated backend user to inject arbitrary SQL. The scope's filter values are interpolated into the conditions statement without parameter binding, so a user with access to a list view whose filter uses this scope and configuration can supply crafted input through the filter's AJAX handler and read arbitrary database contents. No built-in Winter CMS backend views use this scope type and configuration combination, so exploitation requires a third-party plugin to have registered a numberrange filter scope with a conditions key, and a vanilla installation without such plugins is not affected. This issue is fixed in version 1.2.13.