CVE-2026-63179
Last modified
CVE-2026-63179 is a medium-severity vulnerability rated 4.9/10 on the CVSS scale. Winter CMS is a content management system built on the Laravel PHP framework. In versions up to and including 1.2.12, authenticated backend users can disclose arbitrary files readable by the PHP process by injecting @import (inline) directives into LESS source that the backend compiles, because the LESS parser was instantiated without a safe import resolver and fell back to the raw attacker-supplied path when no allowed root matched. EPSS estimates a 0.35% chance of exploitation in the next 30 days.
Description
Winter CMS is a content management system built on the Laravel PHP framework. In versions up to and including 1.2.12, authenticated backend users can disclose arbitrary files readable by the PHP process by injecting @import (inline) directives into LESS source that the backend compiles, because the LESS parser was instantiated without a safe import resolver and fell back to the raw attacker-supplied path when no allowed root matched. The flaw is reachable through four entry points that share the same root cause: the Brand Settings custom_css field, the Editor Settings html_custom_styles field, the Mail Brand Settings colour-picker fields whose values are concatenated into LESS source without escaping, and theme .less, .sass, and .scss assets compiled when served. Both absolute paths and .. traversal outside the asset's own tree were accepted, so an attacker could read any file the web process can access, most significantly the application .env file and the APP_KEY and database credentials it contains. Exploitation requires a backend account holding one of the associated permissions, which are assigned by default to the built-in Developer role. This issue is fixed in version 1.2.13.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| wintercms | winter | < 1.2.13 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2026-63179?
How severe is CVE-2026-63179?
How do I fix CVE-2026-63179?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-6315Use after free in Permissions in Google Chrome on Android pr…8.8
- CVE-2026-6316Use after free in Forms in Google Chrome prior to 147.0.7727…8.8
- CVE-2026-6317Use after free in Cast in Google Chrome prior to 147.0.7727.…8.8
- CVE-2026-63175PlaywrightCapture stored capture-specific configuration and …7.1
- CVE-2026-63177Malcolm is a network traffic analysis tool suite. Prior to v…7.1
- CVE-2026-63178Onyx is an open-source AI platform. Prior to 4.3.0, Onyx Ent…6.5
- CVE-2026-6318Use after free in Codecs in Google Chrome prior to 147.0.772…8.8
- CVE-2026-63187Logto is the modern, open-source auth infrastructure for Saa…6.3
- CVE-2026-63188Logto is the modern, open-source auth infrastructure for Saa…8.7
- CVE-2026-6319Use after free in Payments in Google Chrome on Android prior…7.5
- CVE-2026-6320The Salon Booking System – Free Version plugin for WordPress…7.5
- CVE-2026-6321fast-uri decoded percent-encoded path separators and dot seg…7.5
Are you affected by CVE-2026-63179?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
