{"answers":{"affected":"2 open source packages ship an affected version, including winter/wn-backend-module.","exploited":"There is no known exploitation of CVE-2026-32593 in the wild and no public exploit code.","fix":"Upgrade winter/wn-backend-module to 1.2.13 or later.","what":"CVE-2026-32593 is a medium-severity SQL injection vulnerability in wintercms winter, published on 26 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-32593 and fix it if it is affected.\n\nWhat it is: CVE-2026-32593 is a medium-severity SQL injection vulnerability in wintercms winter, published on 26 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-32593 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- winter/wn-backend-module (Packagist): affected all versions; fixed in 1.2.13\n- winter/wn-backend-module (Packagist): affected all versions; fixed in 1.2.13\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-32593/ (Markdown: https://insights.sbomify.com/CVE-2026-32593/index.md)","id":"CVE-2026-32593","markdown":"https://insights.sbomify.com/CVE-2026-32593/index.md","name":"CVE-2026-32593","record":{"aliases":["GHSA-m7jc-g4rc-jmvh"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Winter CMS","requires_auth":"low_privilege","summary":"Authenticated backend users can inject SQL via AJAX filters in specific plugin configurations, allowing arbitrary database reads.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"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.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Winter: SQL Injection in Backend Filter Widget numberrange Scope via numbersFromAjax","id":"CVE-2026-32593","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"Parse Server GraphQL WebSocket endpoint bypasses security middleware","id":"CVE-2026-32594"},"packages":[{"ecosystem":"Packagist","fixed":["1.2.13"],"introduced":["0"],"last_affected":[],"package":"winter/wn-backend-module","purl":null,"source":"GHSA-m7jc-g4rc-jmvh"},{"ecosystem":"Packagist","fixed":["1.2.13"],"introduced":["0"],"last_affected":[],"package":"winter/wn-backend-module","purl":"pkg:composer/winter/wn-backend-module","source":"GHSA-m7jc-g4rc-jmvh"}],"prev":{"headline":"Mirror-registry: quay: server-side request forgery in proxy cache upstream registry configuration","id":"CVE-2026-32591"},"products":["winter"],"published":"2026-08-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-26","vendors":["wintercms"]},"summary":"Authenticated backend users can inject SQL via AJAX filters in specific plugin configurations, allowing arbitrary database reads.","url":"https://insights.sbomify.com/CVE-2026-32593/"}