CVE-2026-32639

MEDIUMPre-NVD 6.86.8
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 80% 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
6.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Winter CMS is a content management system built on the Laravel PHP framework. In versions up to and including 1.2.12, the CMS section's Theme Editor AJAX handlers did not enforce per-template-type permission checks, allowing a backend user with any single CMS permission to act on template types outside their authorized scope. The CMS controller gated access to the section as a whole using OR-logic across its five permissions, but individual handlers such as onSave(), onDelete(), and onDeleteTemplates() did not verify that the user held the specific permission for the requested template type, so a user with only cms.manage_pages could craft AJAX requests to delete layouts, modify partials, or read content files. Separately, the AssetList widget was registered for any user who passed the controller gate regardless of the cms.manage_assets permission, and its onUpload() handler omitted the theme-validation call present on the other mutating handlers, permitting unauthorized file uploads into the active theme's asset directory. Exploitation requires an authenticated backend account holding at least one of the CMS Theme Editor permissions. This issue is fixed in version 1.2.13.

CVSS v3
6.8
EG Score
6.8(medium)
EG Risk
31(Track)
EG Risk 31/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 computed
Severity68% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
21%
KEV
Not listed

Published

August 12, 2026

Last Modified

September 9, 2026

Advisory Details (4)

Auto-updated Aug 26, 2026
Patch available. Sources: github_commit, github_release, github.
github Patch Available

Broken access control in Theme Editor template management allows cross-template type manipulation and unauthorized asset uploads · Advisory · wintercms/winter · GitHub

https://github.com/wintercms/winter/security/advisories/GHSA-5c4f-9pq9-6c77
github_release Patch Available

v1.2.13

Patch available: wintercms/winter v1.2.13

https://github.com/wintercms/winter/releases/tag/v1.2.13
github_commit Patch Available

commit 5391afa242eb (wintercms/winter)

Patch available: wintercms/winter v1.2.13 (contains commit 5391afa242eb)

https://github.com/wintercms/winter/commit/5391afa242eba3c476869035b7492e50a262c46b
github_commit Patch Available

commit 164c62524e8a (wintercms/winter)

Patch available: wintercms/winter v1.2.13 (contains commit 164c62524e8a)

https://github.com/wintercms/winter/commit/164c62524e8abc153d09c6c35916278bdb746a2b

Vendor Advisories for CVE-2026-32639(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)
PackageVulnerable rangeFixed inDependents
winter/wn-cms-modulev1.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 13× in last 7d / 44× 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.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-18 08:16 UTCEG score recompute
  4. 2026-09-17 19:30 UTCEPSS rescore
  5. 2026-09-17 06:58 UTCEG score recompute
  6. 2026-09-16 14:08 UTCEPSS rescore
  7. 2026-09-16 05:39 UTCEG score recompute
  8. 2026-09-16 05:15 UTCEPSS rescore
  9. 2026-09-15 04:21 UTCEG score recompute
  10. 2026-09-14 02:46 UTCEG score recompute
  11. 2026-09-13 16:47 UTCEPSS rescore
  12. 2026-09-13 01:26 UTCEG score recompute
  13. 2026-09-12 15:01 UTCEPSS rescore
  14. 2026-09-12 00:07 UTCEG score recompute
  15. 2026-09-11 14:52 UTCEPSS rescore
  16. 2026-09-10 22:47 UTCEG score recompute
  17. 2026-09-10 09:34 UTCEPSS rescore
  18. 2026-09-09 05:17 UTCEG score recompute
  19. 2026-09-08 22:00 UTCEPSS rescore
  20. 2026-09-07 16:44 UTCEG score recompute
  21. 2026-09-07 16:01 UTCEPSS rescore
  22. 2026-09-06 14:18 UTCEG score recompute
  23. 2026-09-06 13:47 UTCEPSS rescore
  24. 2026-09-06 13:47 UTCEPSS rescore
  25. 2026-09-05 13:00 UTCEG score recompute
Show 20 more
  1. 2026-09-04 11:30 UTCEG score recompute
  2. 2026-09-04 05:06 UTCEPSS rescore
  3. 2026-09-03 10:11 UTCEG score recompute
  4. 2026-09-02 14:11 UTCEPSS rescore
  5. 2026-09-02 08:38 UTCEG score recompute
  6. 2026-09-01 13:53 UTCEPSS rescore
  7. 2026-09-01 07:19 UTCEG score recompute
  8. 2026-09-01 04:39 UTCEPSS rescore
  9. 2026-09-01 04:39 UTCEPSS rescore
  10. 2026-08-31 06:00 UTCEG score recompute
  11. 2026-08-30 19:17 UTCEPSS rescore
  12. 2026-08-30 04:41 UTCEG score recompute
  13. 2026-08-30 01:22 UTCEPSS rescore
  14. 2026-08-29 03:23 UTCEG score recompute
  15. 2026-08-29 02:48 UTCEG score recompute
  16. 2026-08-28 21:41 UTCEPSS rescore
  17. 2026-08-27 19:44 UTCEG score recompute
  18. 2026-08-27 14:25 UTCEPSS rescore
  19. 2026-08-26 18:25 UTCEG score recompute
  20. 2026-08-12 15:21 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-32639?
CVE-2026-32639 is a medium vulnerability published on August 12, 2026. Winter CMS is a content management system built on the Laravel PHP framework. In versions up to and including 1.2.12, the CMS section's Theme Editor AJAX handlers did not enforce per-template-type permission checks, allowing a backend user with any single CMS permission to act on template types…
When was CVE-2026-32639 disclosed?
CVE-2026-32639 was first published in the National Vulnerability Database on August 12, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-32639 actively exploited?
CVE-2026-32639 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 79.4% of all scored CVEs.
What is the CVSS score of CVE-2026-32639?
CVE-2026-32639 has a CVSS v3 base score of 6.8 (NVD).
How do I remediate CVE-2026-32639?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-32639, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-32639

Explore →

Is Your Infrastructure Affected by CVE-2026-32639?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.