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.
CVE-2026-63179
This medium-severity CVE scores 4.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 71% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.9
- EG Score
- 4.9(medium)
- EG Risk
- 27(Track)EG Risk 27/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity49% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 29%
- KEV
- Not listed
Published
August 20, 2026
Last Modified
September 9, 2026
Advisory Details (4)
Auto-updated Aug 26, 2026v1.2.13
Patch available: wintercms/winter v1.2.13
https://github.com/wintercms/winter/releases/tag/v1.2.13commit 130f0ea43e92 (wintercms/winter)
Patch available: wintercms/winter v1.2.13 (contains commit 130f0ea43e92)
https://github.com/wintercms/winter/commit/130f0ea43e9228bf0d129b481da1cdfbcc4b4456commit af770331c683 (wintercms/storm)
Fix landed in wintercms/storm commit af770331c683 — awaiting tagged release
https://github.com/wintercms/storm/commit/af770331c683e628533a6ec2991285d6e10a4d6cLocal File Inclusion through @import directives in LESS compilation of backend customizable stylesheets and theme assets · Advisory · wintercms/winter · GitHub
https://github.com/wintercms/winter/security/advisories/GHSA-58fp-mcx6-7qf9Vendor Advisories for CVE-2026-63179(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Packagist(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| winter/wn-backend-module | v1.0.473 ... v1.2.9 (26 versions) | 1.2.13 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 40× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-19 00:16 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 02:26 UTCEG score recompute
- 2026-09-17 04:36 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 06:46 UTCEG score recompute
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 08:57 UTCEG score recompute
- 2026-09-14 11:07 UTCEG score recompute
- 2026-09-12 15:28 UTCEG score recompute
- 2026-09-11 17:33 UTCEG score recompute
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 09:37 UTCEPSS rescore
- 2026-09-10 19:14 UTCEG score recompute
- 2026-09-09 01:54 UTCEG score recompute
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-07 19:01 UTCEG score recompute
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 21:11 UTCEG score recompute
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-05 23:14 UTCEG score recompute
- 2026-09-05 15:31 UTCEPSS rescore
- 2026-09-05 01:25 UTCEG score recompute
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-03 05:41 UTCEG score recompute
Show 15 moreShow fewer
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-02 07:17 UTCEG score recompute
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 09:25 UTCEG score recompute
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-08-31 11:35 UTCEG score recompute
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 13:46 UTCEG score recompute
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 15:56 UTCEG score recompute
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-27 18:34 UTCEG score recompute
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 19:23 UTCEG score recompute
- 2026-08-20 19:42 UTCEG score recompute
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-63179?
When was CVE-2026-63179 disclosed?
Is CVE-2026-63179 actively exploited?
What is the CVSS score of CVE-2026-63179?
How do I remediate CVE-2026-63179?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-63179
Is Your Infrastructure Affected by CVE-2026-63179?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.