Skip to main content
VulnerabilityPublished

CVE-2026-32593: Winter · SQL Injection in Backend Filter Widget numberrange Scope via numbersFromAjax

Affects winter/wn-backend-moduleSource GCVE Database

0
Compare
Authoritative record:CVE-2026-32593· Medium 5.9

Not known to be exploited · CVSS 5.9 Medium : upgrade to 1.2.13 when convenient.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.2.13
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade winter/wn-backend-module to 1.2.13.

Affected software

ProductAffectedFixed in
Packagistwinter/wn-backend-moduleAffected
  • <1.2.13
Fixed in
  • 1.2.13

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Winter CMS to version 1.2.13 or later, where this vulnerability is fixed. Since no built-in backend views use the vulnerable scope configuration, installations without third-party plugins registering such filters are not affected. No additional mitigations are required beyond applying the official patch.

Description

Winter CMS versions up to and including 1.2.12 have a SQL injection vulnerability in the backend Filter widget's numberrange scope when configured with a conditions key. This flaw allows an authenticated backend user to inject arbitrary SQL via the filter's AJAX handler, potentially reading arbitrary database contents. Exploitation requires a third-party plugin to register such a filter scope; a vanilla installation is not affected. The issue is fixed in version 1.2.13.

References

Community reviews

Loading reviews…