Answer in brief
CVE-2026-32593 records a Medium severity (CVSS 5.9) vulnerability in Winter: SQL Injection in Backend Filter Widget numberrange Scope via numbersFromAjax. The current sources do not mark it as known exploited. The current feed maps winter/wn-backend-module (composer), wintercms/winter (generic), winter/wn-backend-module (packagist). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.9. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps winter/wn-backend-module (composer), wintercms/winter (generic), winter/wn-backend-module (packagist). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| winter/wn-backend-modulecomposer | <=1.2.12 | 1.2.13 |
| wintercms/wintergeneric | < 1.2.13 | Not reported |
| winter/wn-backend-modulepackagist | >=0 <1.2.13 | 1.2.13 |
Published upstream
Aug 26, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 26, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 12, 2026
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.
Quoted source text, attributed separately from HOL analysis.