CVE-2026-32593: Winter SQL Injection Vulnerability
MODERATECVE-2026-32593 is a MODERATE (CVSS 5.9) sql injection vulnerability (CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')) affecting Winter libraries in the Packagist ecosystem. The issue involves sql injection in backend filter widget numberrange scope via numbersfromajax. Remediation is available by upgrading affected packages to version 1.2.13.
CVE-2026-32593 at a Glance
Security Impact
CVSS: 5.9
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N).
How to Fix CVE-2026-32593
To remediate this vulnerability, upgrade all affected Winter dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade winter/wn-backend-module to 1.2.13
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for winter/wn-backend-module
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-32593, inspect your project dependencies for Winter:
inspect dependencies for winter/wn-backend-module
Analyze the terminal output to locate any version of Winter in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.2.13), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection'), where the product constructs all or part of an sql command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended sql command when it is sent to a downstream component. without sufficient removal or quoting of sql syntax in user-controllable inputs, the generated sql query can cause those inputs to be interpreted as sql instead of ordinary user data. In Winter, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-32593 Affected Winter Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
winter/wn-backend-module
|
Packagist |
< 1.2.13
|
1.2.13
|
References
Frequently Asked Questions
What is CVE-2026-32593?
Which Winter versions are affected?
What version fixes CVE-2026-32593?
Is winter/wn-backend-module affected?
What is the CVSS score of CVE-2026-32593?
What CWE is associated with CVE-2026-32593?
How can I check Packagist dependencies for CVE-2026-32593?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-m7jc-g4rc-jmvh",
"modified" : "2026-08-12T14:41:13Z",
"published" : "2026-08-12T14:41:13Z",
"aliases" : [ "CVE-2026-32593" ],
"summary" : "Winter: SQL Injection in Backend Filter Widget numberrange Scope via numbersFromAjax",
"details" : "## Impact\n\nThe 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.\n\nTo 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.\n\n## Patches\n\nThis issue has been fixed in Winter CMS v1.2.13.\n\n## Workarounds\n\nIf users cannot upgrade, they may apply commit https://github.com/wintercms/winter/commit/50713de95adf5298536d93f4d999652525d36d43 to your Winter CMS\ninstallation manually to resolve this issue.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Packagist",
"name" : "winter/wn-backend-module"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "1.2.13"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 1.2.12"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/wintercms/winter/security/advisories/GHSA-m7jc-g4rc-jmvh"
}, {
"type" : "WEB",
"url" : "https://github.com/wintercms/winter/commit/50713de95adf5298536d93f4d999652525d36d43"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/wintercms/winter"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-89" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-08-12T14:41:13Z",
"nvd_published_at" : null
}
}